Re: [GSoC] My Git Dev Blog – Week 8
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Jul 18, 2021, 09:26 UTC
- Message-ID
- <CAP8UFD1bGm8r_M9_gLEtSf3EAKseHySJWhMOoJjGO4xy6R2+9Q@mail.gmail.com>
- 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:
Show 11 quoted lines
> > ... 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.