From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Atharva Raykar <raykar.ath@gmail.com>,
Emily Shaffer <emilyshaffer@google.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
Shourya Shukla <periperidip@gmail.com>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Prathamesh Chavan <pc44800@gmail.com>
Subject: Re: [PATCH v4] submodule--helper: run update procedures from C
Date: Tue, 07 Sep 2021 17:14:30 -0700 [thread overview]
Message-ID: <xmqqk0jr9b4p.fsf@gitster.g> (raw)
In-Reply-To: <20210824140609.1496-1-raykar.ath@gmail.com> (Atharva Raykar's message of "Tue, 24 Aug 2021 19:36:09 +0530")
Atharva Raykar <raykar.ath@gmail.com> writes:
> * Fix error message handling of the output of 'run-update-procedure'. While at
> it, ensure the "checkout" mode error message is stored and printed
> appropriately.
>
> * In 'run_update_command()' switch from 'run_command()' to
> 'run_command_v_opt_cd_env()' to ensure quoted command update modes are handled
> correctly.
>
> * Code style and hygiene changes.
>
> * Introduce a NEEDSWORK comment, because the printf() and error return is
> correct only because the shell caller in the other end redirects it to the
> correct output stream. Once we switch this completely to C (ie, in the
> follow-up series), I need to remember to die() instead (or print to stderr) to
> reproduce the original behaviour.
I didn't see anybody comment on this round (and do not think I saw
anything glaringly wrong).
Is everybody happy with this version? I am about to mark it for
'next' in the next issue of "What's cooking" report, so please
holler if I should wait.
Thanks.
prev parent reply other threads:[~2021-09-08 0:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 13:40 [GSoC] [PATCH] submodule--helper: run update procedures from C Atharva Raykar
2021-07-23 9:37 ` Ævar Arnfjörð Bjarmason
2021-07-23 16:59 ` Atharva Raykar
2021-08-04 8:35 ` Atharva Raykar
2021-08-02 13:06 ` [GSoC] [PATCH v2] " Atharva Raykar
2021-08-02 18:50 ` Shourya Shukla
2021-08-03 8:46 ` Atharva Raykar
2021-08-03 10:07 ` Atharva Raykar
2021-08-13 7:56 ` [GSoC] [PATCH v3] " Atharva Raykar
2021-08-13 18:32 ` Junio C Hamano
2021-08-24 8:58 ` Atharva Raykar
2021-08-24 14:06 ` [PATCH v4] " Atharva Raykar
2021-09-08 0:14 ` Junio C Hamano [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqk0jr9b4p.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=pc44800@gmail.com \
--cc=periperidip@gmail.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.
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 NNTP newsgroup(s).