git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Atharva Raykar <raykar.ath@gmail.com>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, gitscale@google.com
Subject: Re: Submodules UX overhaul update (was: What's cooking in git.git (Oct 2021, #03; Mon, 11))
Date: Wed, 13 Oct 2021 10:50:23 +0530	[thread overview]
Message-ID: <m2h7dlij88.fsf@gmail.com> (raw)
In-Reply-To: <YWYHCnpPnrjwTjhA@google.com>


Emily Shaffer <emilyshaffer@google.com> writes:

> As I promised in IRC yesterday, here's an attempt to filter this into a
> submodules newsletter of sorts.
>
> For context on the broader submodules effort I'm discussing in this
> note, please see the design doc:
> https://lore.kernel.org/git/YHofmWcIAidkvJiD@google.com/
>
> I'm aware there are other submodule efforts ongoing too, but in this
> letter I've highlighted ones that are necessary for the above-linked
> design doc. Selfish, I know. ;)
>
> On Mon, Oct 11, 2021 at 05:14:14PM -0700, Junio C Hamano wrote:
>> [Stalled]
>>
>> * ar/submodule-update (2021-09-20) 8 commits
>>  . submodule--helper: rename helper functions
>>  . submodule--helper: remove unused helpers
>>  . submodule--helper: remove update-clone subcommand
>>  . submodule: move core cmd_update() logic to C
>>  . submodule--helper: refactor get_submodule_displaypath()
>>  . submodule--helper: rename helpers for update-clone
>>  . submodule--helper: get remote names from any repository
>>  . submodule--helper: split up ensure_core_worktree()
>>
>>  Rewrite of "git submodule update" in C.
>>
>>  Kicked out of 'seen' to make room for es/superproject-aware-submodules
>>  which is among the topics this topic stomps on.
>
> Mentioning this series in the "newsletter" since I'm aware that I'm
> blocking it with es/superproject-aware-submodules. I have it open in
> another tab as I type and plan to send a reroll today or tomorrow.

I am not sure if this will be helpful or not, but today I sent a reroll
of my topic, and while I was at it, I tried to reapply your series and
my series on the up-to-date master to see where conflicts appear. I have
written a note about it in my cover letter [1]. I hope it can be helpful
in some way!

[1] https://lore.kernel.org/git/20211013051805.45662-1-raykar.ath@gmail.com/

  reply	other threads:[~2021-10-13  5:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12  0:14 What's cooking in git.git (Oct 2021, #03; Mon, 11) Junio C Hamano
2021-10-12 22:07 ` Submodules UX overhaul update (was: What's cooking in git.git (Oct 2021, #03; Mon, 11)) Emily Shaffer
2021-10-13  5:20   ` Atharva Raykar [this message]
2021-10-13 13:28 ` ab/mark-leak-free-tests Ævar Arnfjörð Bjarmason
2021-10-13 13:33 ` ab/unpack-trees-leakfix Ævar Arnfjörð Bjarmason
2021-10-13 13:43 ` What's cooking in git.git (Oct 2021, #03; Mon, 11) Ævar Arnfjörð Bjarmason
2021-10-13 13:47 ` ab/parse-options-cleanup Ævar Arnfjörð Bjarmason
2021-10-13 22:35 ` What's cooking in git.git (Oct 2021, #03; Mon, 11) Junio C Hamano
2021-10-14 14:42   ` js/retire-preserve-merges, was " Johannes Schindelin
2021-10-14 15:50   ` Ævar Arnfjörð Bjarmason
2021-10-14 17:09     ` Junio C Hamano

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=m2h7dlij88.fsf@gmail.com \
    --to=raykar.ath@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitscale@google.com \
    --cc=gitster@pobox.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).