git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Glen Choo <chooglen@google.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: gc/submodule-update-part2 (was Re: What's cooking in git.git (Mar 2022, #04; Thu, 17))
Date: Tue, 22 Mar 2022 09:05:00 -0700	[thread overview]
Message-ID: <kl6ly212j7mb.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <xmqqv8wcizi4.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

> * gc/submodule-update-part2 (2022-03-16) 8 commits
>  - submodule--helper: remove forward declaration
>  - submodule: move core cmd_update() logic to C
>  - submodule--helper: reduce logic in run_update_procedure()
>  - submodule--helper: teach update_data more options
>  - builtin/submodule--helper.c: rename option struct to "opt"
>  - submodule update: use die_message()
>  - submodule--helper: run update using child process struct
>  - Merge branch 'gc/submodule-update-part1' into gc/submodule-update-part2
>  (this branch uses gc/submodule-update-part1.)
>
>  Move more "git submodule update" to C.
>  source: <20220315210925.79289-1-chooglen@google.com>

Ævar looked at part 1, and I think he'd be interested in part 2 too.
That said, I'd welcome feedback from anyone :) This series is fairly
simple and doesn't require knowledge of previous attempts to convert
"submodule update".

  parent reply	other threads:[~2022-03-22 16:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 11:34 What's cooking in git.git (Mar 2022, #04; Thu, 17) Junio C Hamano
2022-03-22  1:25 ` Taylor Blau
2022-03-23 18:27   ` Junio C Hamano
2022-03-23 19:20     ` Taylor Blau
2022-03-23 21:37       ` Junio C Hamano
2022-03-23 21:47         ` Taylor Blau
2022-03-22 16:05 ` Glen Choo [this message]
2022-03-22 18:24 ` Jeff Hostetler
2022-03-23 18:28   ` Junio C Hamano
2022-03-23 20:14     ` Jeff Hostetler

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=kl6ly212j7mb.fsf@chooglen-macbookpro.roam.corp.google.com \
    --to=chooglen@google.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --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).