From: Taylor Blau <me@ttaylorr.com>
To: Shubham Mishra <shivam828787@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
Taylor Blau <me@ttaylorr.com>,
Plato Kiorpelidis <kioplato@gmail.com>, git <git@vger.kernel.org>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [GSoC] Contributor candidate introduction
Date: Wed, 6 Apr 2022 11:40:56 -0400 [thread overview]
Message-ID: <Yk20iKECF5vDtWQL@nand.local> (raw)
In-Reply-To: <CAC316V6mDowYpptox3KxYycpwpiQhW+LSmNOx8_F_8LKBG2gUw@mail.gmail.com>
On Wed, Apr 06, 2022 at 07:41:35PM +0530, Shubham Mishra wrote:
> Hi,
>
> As the topic begans, I think I should also give my updates. Last week
> I spend time around "Croaring" library and right now, I start working
> on the initial version of proposal which I am planning to share by end
> of this week. I think if it's possible to split it into two, We can
> look forward to it with I am okay with picking other project involving
> bitmap too but only issue, I have to start again from scratch :)
Sounds great; I think that having a proposal of how/if we should use
Roaring+Run bitmaps in Git will be useful in its own right.
I expect that it will generate some useful discussion, and provide a
good roadmap for any contributor to get started working on it. Let's see
how the proposal develops and adjust, split or not split the GSoC
project as necessary.
Thanks,
Taylor
next prev parent reply other threads:[~2022-04-06 17:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 21:43 [GSoC] Contributor candidate introduction Plato Kiorpelidis
2022-04-05 21:59 ` Taylor Blau
2022-04-06 6:25 ` Christian Couder
2022-04-06 14:11 ` Shubham Mishra
2022-04-06 15:40 ` Taylor Blau [this message]
2022-04-06 15:43 ` Taylor Blau
2022-04-06 20:11 ` Kaartic Sivaraam
2022-04-07 7:16 ` Christian Couder
2022-04-07 9:25 ` Abhradeep Chakraborty
2022-04-08 20:34 ` Taylor Blau
2022-04-08 20:46 ` Junio C Hamano
2022-04-13 20:55 ` Taylor Blau
2022-04-15 21:01 ` Plato Kiorpelidis
2022-04-18 17:54 ` Kaartic Sivaraam
2022-04-18 18:06 ` Abhradeep Chakraborty
2022-04-19 4:38 ` Shubham Mishra
2022-04-19 15:54 ` Abhradeep Chakraborty
2022-04-18 18:24 ` Kaartic Sivaraam
2022-04-19 13:16 ` Jayati Shrivastava
2022-04-19 17:40 ` Kaartic Sivaraam
2022-04-20 13:16 ` Labnan Khalid Masum
2022-04-20 19:40 ` Kaartic Sivaraam
2022-04-21 8:58 ` Christian Couder
2022-04-18 18:33 ` Plato Kiorpelidis
2022-05-09 6:44 ` Kaartic Sivaraam
2022-05-09 15:12 ` Shubham Mishra
2022-05-09 16:36 ` Taylor Blau
2022-05-09 20:13 ` Plato Kiorpelidis
-- strict thread matches above, loose matches on Subject: below --
2022-04-05 21:30 Plato Kiorpelidis
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yk20iKECF5vDtWQL@nand.local \
--to=me@ttaylorr.com \
--cc=chriscool@tuxfamily.org \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--cc=kioplato@gmail.com \
--cc=shivam828787@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).