git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Atharva Raykar <raykar.ath@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Git List <git@vger.kernel.org>,
	Shourya Shukla <periperidip@gmail.com>,
	Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Subject: Re: [GSoC] My Git Dev Blog — Week 6
Date: Mon, 28 Jun 2021 13:18:30 +0530	[thread overview]
Message-ID: <F28CA742-014E-4279-8A0C-825DF773FA33@gmail.com> (raw)
In-Reply-To: <CAP8UFD2xCzJ7hxd_Of0FWnPKGzm9j9DizK55GyMhedzGgbs8gA@mail.gmail.com>

On 28-Jun-2021, at 03:37, Christian Couder <christian.couder@gmail.com> wrote:
> 
> On Sun, Jun 27, 2021 at 1:24 PM Atharva Raykar <raykar.ath@gmail.com> wrote:
>> 
>> Here's the latest instalment of my weekly Git blog:
> 
> s/instalment/installment/

Instalment is the commonwealth spelling:
https://wikidiff.com/instalment/installment

>> https://atharvaraykar.me/gitnotes/week6
> 
> Great, thanks!
> 
> Small nit: s/has not not yet/has not yet/

Thanks, I'll update it.

> About "This kind of an invocation was done before in the context of
> submodules, but it does not look reusable to me because it seems to
> have side effects, that meddle with the repository’s object store."
> couldn't a commit walk do the job (see
> Documentation/MyFirstObjectWalk.txt)?

I did have a look at it (not very thorough, though), and I immediately
felt that it was too low-level to be a drop-in replacement for
'is_tip_reachable'. I'll have a more thorough look at it though, and
see if I can make that work out nicely.

  reply	other threads:[~2021-06-28  7:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27 11:24 [GSoC] My Git Dev Blog — Week 6 Atharva Raykar
2021-06-27 17:01 ` Felipe Contreras
2021-06-28  7:35   ` Atharva Raykar
2021-06-27 22:07 ` Christian Couder
2021-06-28  7:48   ` Atharva Raykar [this message]
     [not found] ` <CACdWUYWOsU+oHDNnur_NCSBuMfea95rKqrS5z2x-JRc_C0iyfg@mail.gmail.com>
2021-06-28 17:01   ` Atharva Raykar

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=F28CA742-014E-4279-8A0C-825DF773FA33@gmail.com \
    --to=raykar.ath@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=periperidip@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).