git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Victoria Dye <vdye@github.com>
To: Christian Couder <christian.couder@gmail.com>,
	Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: git <git@vger.kernel.org>, Derrick Stolee <stolee@gmail.com>,
	Hariom verma <hariom18599@gmail.com>
Subject: Re: GSoC 2023
Date: Mon, 6 Feb 2023 08:58:26 -0800	[thread overview]
Message-ID: <b8f90d73-8c49-554c-1109-92d8713d1c29@github.com> (raw)
In-Reply-To: <CAP8UFD32nDLR8BrhmeTpyraX3QBrc=U1ody+qgyMVY+_-HrASA@mail.gmail.com>

Christian Couder wrote:
> I removed the "Reachability bitmap improvements" idea but left the 2 others:
> 
>   - More Sparse Index Integrations (I removed `git mv` in the list of
> commands that need to be improved though)
>   - Unify ref-filter formats with other pretty formats
> 
> On both of them I removed all possible mentors except me though. They
> are welcome to tell me that they should be added back.
> 

After mulling it over, I'd like to sign up as a mentor again this year for
"More Sparse Index Integrations" - feel free to add me back to the
application. AFAIK I'd be solo-mentoring for this project (although I'm
happy to work with a co-mentor if anyone's interested!).

Thanks!
-Victoria

  parent reply	other threads:[~2023-02-06 16:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17  9:34 GSoC 2023 Christian Couder
2023-01-23 17:41 ` Kaartic Sivaraam
2023-01-24 16:38   ` Christian Couder
2023-01-24 19:18     ` Taylor Blau
2023-02-05 19:50     ` Hariom verma
2023-02-06 17:44       ` Kaartic Sivaraam
2023-02-07 11:58         ` Christian Couder
2023-02-06 16:58     ` Victoria Dye [this message]
2023-02-06 17:48       ` Kaartic Sivaraam
2023-02-07 21:04         ` Taylor Blau
2023-03-09 10:17 ` Christian Couder
2023-03-09 17:19   ` Kaartic Sivaraam
2023-03-09 18:45     ` Hariom verma
2023-03-10  0:56       ` Kaartic Sivaraam
2023-03-10 12:38     ` Christian Couder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b8f90d73-8c49-554c-1109-92d8713d1c29@github.com \
    --to=vdye@github.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hariom18599@gmail.com \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=stolee@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).