git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Glen Choo <chooglen@google.com>
To: Atharva Raykar <raykar.ath@gmail.com>,
	Emily Shaffer <emilyshaffer@google.com>
Cc: Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>,
	gitscale@google.com
Subject: Re: Submodule UX overhaul update (was: What's cooking in git.git (Jan 2022, #07; Mon, 24))
Date: Wed, 26 Jan 2022 09:50:44 -0800	[thread overview]
Message-ID: <kl6lzgniz8qz.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <CADi-XoThCqfvPnBd0p6yAhrtotK_3z2pQQMugWPsYpHLbXge7w@mail.gmail.com>

Atharva Raykar <raykar.ath@gmail.com> writes:

> 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.
>
> 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.
>
> [0] https://github.com/tfidfwastaken/git/commits/submodule-update-on-es-superproject-aware

No worries! It's more like we don't want your good work to go to
waste than a blocker :)

Emily is planning to reroll her series and in all likelihood, I'll
attempt the rebase of ar/submodule-update when that's done.

  parent reply	other threads:[~2022-01-26 17:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 19:39 What's cooking in git.git (Jan 2022, #07; Mon, 24) Junio C Hamano
2022-01-25 19:45 ` Submodule UX overhaul update (was: What's cooking in git.git (Jan 2022, #07; Mon, 24)) Emily Shaffer
2022-01-26 14:09   ` Ævar Arnfjörð Bjarmason
2022-01-26 17:27     ` Emily Shaffer
2022-01-26 15:16   ` Kaartic Sivaraam
2022-01-26 16:35   ` Atharva Raykar
2022-01-26 17:43     ` Emily Shaffer
2022-01-26 17:50     ` Glen Choo [this message]
2022-01-28  7:40 ` ps/avoid-unnecessary-hook-invocation-with-packed-refs (Was: " Patrick Steinhardt
2022-01-28 21:14   ` ps/avoid-unnecessary-hook-invocation-with-packed-refs Junio C Hamano
2022-01-31  9:50     ` flags types/names (was: ps/avoid-unnecessary-hook-invocation-with-packed-refs) Han-Wen Nienhuys
2022-01-31 17:13       ` flags types/names Junio C Hamano
2022-01-28 22:31 ` What's cooking in git.git (Jan 2022, #07; Mon, 24) brian m. carlson
2022-02-04  0:27   ` Junio C Hamano
2022-02-04 17:27     ` René Scharfe
2022-02-02 11:28 ` ab/auto-detect-zlib-compress2 (was: What's cooking in git.git (Jan 2022, #07; Mon, 24)) Ævar Arnfjörð Bjarmason

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=kl6lzgniz8qz.fsf@chooglen-macbookpro.roam.corp.google.com \
    --to=chooglen@google.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitscale@google.com \
    --cc=gitster@pobox.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).