From: Christian Couder <christian.couder@gmail.com>
To: Atharva Raykar <raykar.ath@gmail.com>
Cc: Git List <git@vger.kernel.org>,
Shourya Shukla <periperidip@gmail.com>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Subject: Re: My Git Dev Blog - Week 9
Date: Sun, 18 Jul 2021 15:15:35 +0200 [thread overview]
Message-ID: <CAP8UFD0NCQ5w_3GtT_xHr35i7h8BuLX4UcHNY6VHPGREmDVObA@mail.gmail.com> (raw)
In-Reply-To: <ED260A04-153A-46D5-8A84-CF517085DEC9@gmail.com>
On Sun, Jul 18, 2021 at 1:59 PM Atharva Raykar <raykar.ath@gmail.com> wrote:
>
> Here's my latest blog post:
> https://atharvaraykar.me/gitnotes/week9
Great!
> 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
My wild guess about why is_submodule_active() might not be working as
expected is that submodule_from_path() uses the submodule cache which
might not be properly updated when a submodule is initialized by a
subprocess.
> The rest of the post talks about my project progress so far, and how I
> avoided the above problem entirely for now by taking a different approach.
Nice that you found a possible better way!
next prev parent reply other threads:[~2021-07-18 13:15 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 [this message]
2021-07-19 8:57 ` Atharva Raykar
2021-07-18 19:19 ` Kaartic Sivaraam
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP8UFD0NCQ5w_3GtT_xHr35i7h8BuLX4UcHNY6VHPGREmDVObA@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--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.
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).