Re: Submodule UX overhaul update (was: What's cooking in git.git (Jan 2022, #07; Mon, 24))

From: Emily Shaffer <emilyshaffer@google.com>
Date: Jan 26, 2022, 17:43 UTC
Message-ID: <YfGIQpJJ3qGro+FM@google.com>
In-Reply-To: <CADi-XoThCqfvPnBd0p6yAhrtotK_3z2pQQMugWPsYpHLbXge7w@mail.gmail.com>

On Wed, Jan 26, 2022 at 10:05:38PM +0530, Atharva Raykar wrote:

Show 28 quoted lines

> 
> On Wed, Jan 26, 2022 at 2:02 PM Emily Shaffer <emilyshaffer@google.com> wrote:
> >
> > Finally finding the time to write up another "what's cooking as pertain
> > to overhauling submodules UX" reply.
> >
> > [...]
> > >  Rewrite of "git submodule update" in C.
> > >
> > >  Expecting a reroll?
> > >  cf. <YWiXL+plA7GHfuVv@google.com>
> > >  source: <20211013051805.45662-10-raykar.ath@gmail.com>
> >
> > Sounds like Glen is interested in this series with regard to some edge
> > cases about cloning newly added submodules during a 'git fetch
> > --recurse-submodules'. I'm curious to hear from Atharva about the status
> > of this work :)
> 
> Hi!
> I'll preface by saying that I haven't had the time to keep this up to date
> with the other submodule developments.
> 
> My recollection was that this series had some small conflicts with
> es/superproject-aware-submodules. The last thing I had done was to
> rebase this on top of es/superproject-aware-submodules [0] and try to
> fix those conflicts. I had not rerolled that branch as a patch series yet,
> because I had thought that superproject-aware-submodules was still
> in flux.

Thanks! That makes sense. Oof. :(

> 
> I won't be able to actively work on this in the near future. Feel free to
> pick this up in case this patch is a blocker for yours or Glen's work.

Thanks for the update - that helps!

 - Emily

> 
> [0] https://github.com/tfidfwastaken/git/commits/submodule-update-on-es-superproject-aware