git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Glen Choo <chooglen@google.com>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Emily Shaffer" <emilyshaffer@google.com>
Subject: Re: ar/submodule-update (wa Re: What's cooking in git.git (Feb 2022, #06; Wed, 23))
Date: Thu, 24 Feb 2022 11:55:06 -0800	[thread overview]
Message-ID: <xmqqo82wkpk5.fsf@gitster.g> (raw)
In-Reply-To: <kl6lmtig40l4.fsf@chooglen-macbookpro.roam.corp.google.com> (Glen Choo's message of "Fri, 25 Feb 2022 01:48:55 +0800")

Glen Choo <chooglen@google.com> writes:

> I've dug a little deeper, and I think my plan to reroll this as two
> series [1] makes sense:
>
> 1. Small, obvious conversions from sh->C.
> 2. Finalizing the conversion.
>
> (1) has only trivial conflicts, and is relatively easy to review, so I
> expect that to go through quickly.
>
> This should also buy some time to finalize those other topics and
> hopefully make coordination simpler.

Wonderful.


  reply	other threads:[~2022-02-24 19:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  3:40 What's cooking in git.git (Feb 2022, #06; Wed, 23) Junio C Hamano
2022-02-24  9:08 ` ab/commit-plug-leaks + ab/diff-free-more (was: What's cooking in git.git (Feb 2022, #06; Wed, 23)) Ævar Arnfjörð Bjarmason
2022-02-24 23:38   ` ab/commit-plug-leaks + ab/diff-free-more Junio C Hamano
2022-02-24  9:11 ` ab/c99 + ab/hook-tests (was: What's cooking in git.git (Feb 2022, #06; Wed, 23)) Ævar Arnfjörð Bjarmason
2022-02-24  9:18 ` ab/object-file-api-updates " Ævar Arnfjörð Bjarmason
2022-02-24 17:48 ` ar/submodule-update (wa " Glen Choo
2022-02-24 19:55   ` Junio C Hamano [this message]
2022-02-24 19:11 ` jc/cat-file-batch-commands (was: " John Cai

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=xmqqo82wkpk5.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=chooglen@google.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    /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).