git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Plato Kiorpelidis <kioplato@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: Christian Couder <christian.couder@gmail.com>,
	Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	git <git@vger.kernel.org>,
	Shubham Mishra <shivam828787@gmail.com>,
	Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [GSoC] Contributor candidate introduction
Date: Sat, 16 Apr 2022 00:01:08 +0300	[thread overview]
Message-ID: <CAO2gv83WXPmABfVu_YR57rJg8sJ7mv-pUuXDpxYw644gcRCtYw@mail.gmail.com> (raw)
In-Reply-To: <Ylc4rWZf380FlEbj@nand.local>

On Wed, Apr 13, 2022 at 11:55 PM Taylor Blau <me@ttaylorr.com> wrote:
>
> Hi Plato,

Hey Taylor,

>
> On Fri, Apr 08, 2022 at 04:34:11PM -0400, Taylor Blau wrote:
> > Instead, let's keep the project as-is, and have the accepted student
> > focus on one of the first two bullet points, taking into account that
> > we'll first want to spend some time thinking about whether or not the
> > current .bitmap format is appropriate given the proposed changes.
>
> If this sounds interesting to you, I would encourage you to submit a
> proposal similar to the ones in

Yes, it does sound interesting to me because it's an experimental
project. I'm working exclusively on my proposal for the past week
reading papers and benchmarks, while writing digests about them
to include in my proposal, in favor of roaring method. As you also
said, having a proposal with references and digests about previous
work, discussions and papers does help regardless of being selected.

Technical question: will roaring bitmaps' random access feature help
with introducing the "table of contents" feature? Or is it bitmap
compression agnostic?

>
>     https://lore.kernel.org/git/20220406200440.27010-1-chakrabortyabhradeep79@gmail.com/
>     https://lore.kernel.org/git/20220409184350.1124-3-shivam828787@gmail.com/

Thanks, I've already read both of them and used them as guideline for
my proposal.

>
> Feel free to take a look at mine and Kaartic's responses to each of
> those, two, since they may influence your planning / which sub-project
> sounds most interesting / etc.

I saw your and Kaartic's reviews and incorporated them into my proposal.

>
> Thanks,
> Taylor

Thanks,
Plato

  reply	other threads:[~2022-04-15 21:04 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
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 [this message]
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=CAO2gv83WXPmABfVu_YR57rJg8sJ7mv-pUuXDpxYw644gcRCtYw@mail.gmail.com \
    --to=kioplato@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=me@ttaylorr.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).