git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philip Oakley <philipoakley@iee.email>
To: Taylor Blau <me@ttaylorr.com>,
	Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
Cc: git <git@vger.kernel.org>, Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Subject: Re: [GSoC][RFC][PROPOSAL] Reachability bitmap improvements
Date: Thu, 14 Apr 2022 15:24:29 +0100	[thread overview]
Message-ID: <fc0015ac-9ad4-d3b4-39ee-0bf4f9c99fa0@iee.email> (raw)
In-Reply-To: <YlckmDHRAYnE1J5t@nand.local>

Hi Abhradeep,


On 13/04/2022 20:29, Taylor Blau wrote:
>> Though I had read many documentations, I was still not able to fully
>> understand the terminologies (like `refs`, `packfiles`, `blobs`, `trees`
>> etc.). (ProGit)[https://git-scm.com/book/en/v2] helped me tremendously here.
>> I read the full book and it cleared almost every doubt that came into my mind.
> Terrific! I am really glad that the MyFirst... documents were helpful
> and made it easier for you to contribute. The ProGit book is a great
> resource, too.
>
> If you are looking for more resources, I would encourage you to search
> around for blog posts written by Git contributors, particularly related
> to reachability bitmaps (at least for this GSoC project). Some helpful
> places to start there would be:
>
>     https://github.blog/2015-09-22-counting-objects/
>     https://github.blog/2021-04-29-scaling-monorepo-maintenance/
>
It's also worth looking at the Git Rev News articles and light reading links
     https://git.github.io/rev_news/ and
     https://git.github.io/rev_news/archive/
--
Philip.

  parent reply	other threads:[~2022-04-14 14:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 20:04 [GSoC][RFC][PROPOSAL] Reachability bitmap improvements Abhradeep Chakraborty
2022-04-13 19:29 ` Taylor Blau
2022-04-14  7:58   ` Abhradeep Chakraborty
2022-04-14 14:24   ` Philip Oakley [this message]
2022-04-15  5:28     ` Abhradeep Chakraborty
  -- strict thread matches above, loose matches on Subject: below --
2022-04-06 20:09 Abhradeep Chakraborty
2022-04-13 20:03 ` Kaartic Sivaraam
2022-04-14  8:20   ` Abhradeep Chakraborty
2022-04-14 20:29     ` Kaartic Sivaraam
2022-04-15  5:23       ` Abhradeep Chakraborty
2022-04-06 20:46 Abhradeep Chakraborty
2022-04-19  0:10 [GSoC][RFC][Proposal] " 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

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

  git send-email \
    --in-reply-to=fc0015ac-9ad4-d3b4-39ee-0bf4f9c99fa0@iee.email \
    --to=philipoakley@iee.email \
    --cc=chakrabortyabhradeep79@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=me@ttaylorr.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).