git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Atharva Raykar <raykar.ath@gmail.com>, Git List <git@vger.kernel.org>
Cc: Christian Couder <christian.couder@gmail.com>,
	Shourya Shukla <periperidip@gmail.com>
Subject: Re: My Git Dev Blog - Week 9
Date: Mon, 19 Jul 2021 00:49:29 +0530	[thread overview]
Message-ID: <09edd920-e9ef-f8f9-79e6-d27badd2e5a6@gmail.com> (raw)
In-Reply-To: <ED260A04-153A-46D5-8A84-CF517085DEC9@gmail.com>

Hi Atharva and all,

On 18/07/21 5:29 pm, Atharva Raykar wrote:
> Here's my latest blog post:
> https://atharvaraykar.me/gitnotes/week9
> 

Nice blog!

> A part that may be interesting to list readers:
> 
> - In one section of the blog, I describe the problem of the git
>    submodule configuration not updating properly, when I launch
>    a subprocess that first initialises the submodule. I will
>    appreciate it if someone has a possible explanation for the
>    issue I faced at:
>    https://atharvaraykar.me/gitnotes/week9#launching-the-init-part-as-a-subprocess
> 

Christian mentioned a possible reason. I'll try to take a look
later and see if I could find anything.

> Passing the superprefix explicitly

My gut instinct tells me we could get away without having to go this way but
I haven't yet been able to figure out how. How 'prefix', 'super-prefix' and
'recursive-prefix' is still puzzling me. In case anyone has knowledge about
this please chime in and enlighten us. It would be very helpful.

> I am also waiting on my list patch to land on master, so that I can
> then send the next patch for the submodule add conversion.

I think you don't have to wait until it lands on 'master'. Now that it
is set to merge to 'next', I believe it should be fine for you to send
the rest of the series to the list. Just make sure you mention the
dependency of the series on the one you've already sent to the list.

> Have a great day!
>

Thanks! Hope you have a great weak ahead and do well in your exams.

-- 
Sivaraam

  parent reply	other threads:[~2021-07-18 19:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 11:59 My Git Dev Blog - Week 9 Atharva Raykar
2021-07-18 13:15 ` Christian Couder
2021-07-19  8:57   ` Atharva Raykar
2021-07-18 19:19 ` Kaartic Sivaraam [this message]
2021-07-19  2:58   ` Kaartic Sivaraam
2021-07-19  8:48     ` Atharva Raykar
2021-07-19  0:51 ` Bagas Sanjaya
2021-07-19  8:53   ` 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

  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=09edd920-e9ef-f8f9-79e6-d27badd2e5a6@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=periperidip@gmail.com \
    --cc=raykar.ath@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).