From: Christian Couder <christian.couder@gmail.com>
To: Atharva Raykar <raykar.ath@gmail.com>
Cc: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Git List <git@vger.kernel.org>,
Shourya Shukla <periperidip@gmail.com>
Subject: Re: [GSoC] My Git Dev Blog – Week 8
Date: Sun, 18 Jul 2021 11:26:48 +0200 [thread overview]
Message-ID: <CAP8UFD1bGm8r_M9_gLEtSf3EAKseHySJWhMOoJjGO4xy6R2+9Q@mail.gmail.com> (raw)
In-Reply-To: <D3F13902-A7DD-4186-8444-45FD9260CBC8@gmail.com>
On Tue, Jul 13, 2021 at 10:46 AM Atharva Raykar <raykar.ath@gmail.com> wrote:
>
> On 13-Jul-2021, at 13:48, Kaartic Sivaraam <kaartic.sivaraam@gmail.com> wrote:
> > ... Alternatively, you could explore how other sub-commands
> > handle recursing into submodules. To me it looks like they handle it by spawning
> > a sub-process is likely the easiest approach for achieving recursion. That would
> > solve the super-prefix problem as you have observed.
>
> Yes, I was hoping I would not have to spawn a subprocess for recursing on
> update, and it does look theoretically possible--it would require changing
> a lot of of existing code to use functions taking a repository objects
> rather than assuming 'the_repository'. But since that was outside the scope
> of my project, I did it like the other implementations that spawned a new
> process for the recursion of 'update'.
Yeah, it's definitely outside the scope of your project. So it's ok to
spawn a new process.
next prev parent reply other threads:[~2021-07-18 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 11:18 [GSoC] My Git Dev Blog – Week 8 Atharva Raykar
2021-07-13 8:18 ` Kaartic Sivaraam
2021-07-13 8:46 ` Atharva Raykar
2021-07-18 9:26 ` Christian Couder [this message]
2021-07-18 17:39 ` Kaartic Sivaraam
2021-07-19 7:04 ` 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=CAP8UFD1bGm8r_M9_gLEtSf3EAKseHySJWhMOoJjGO4xy6R2+9Q@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.
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).