git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hariom verma <hariom18599@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	git <git@vger.kernel.org>, Derrick Stolee <stolee@gmail.com>,
	Victoria Dye <vdye@github.com>
Subject: Re: GSoC 2023
Date: Mon, 6 Feb 2023 01:20:15 +0530	[thread overview]
Message-ID: <CA+CkUQ-t3-jOaGE4yMHXxREBs3-t35NCAJ3VTSnMSq5072rsBg@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD32nDLR8BrhmeTpyraX3QBrc=U1ody+qgyMVY+_-HrASA@mail.gmail.com>

Hi,

On Tue, Jan 24, 2023 at 10:08 PM Christian Couder
<christian.couder@gmail.com> 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.

I'm positive that I'll be available by the time the GSoC contribution
officially starts.
You can add me back to "Unify ref-filter formats with other pretty formats".
I would be happy to co-mentor it with you.

Thanks,
Hariom

  parent reply	other threads:[~2023-02-05 19:50 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 [this message]
2023-02-06 17:44       ` Kaartic Sivaraam
2023-02-07 11:58         ` Christian Couder
2023-02-06 16:58     ` Victoria Dye
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=CA+CkUQ-t3-jOaGE4yMHXxREBs3-t35NCAJ3VTSnMSq5072rsBg@mail.gmail.com \
    --to=hariom18599@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=stolee@gmail.com \
    --cc=vdye@github.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).