From: Junio C Hamano <gitster@pobox.com>
To: Nika Layzell <nika@thelayzells.com>
Cc: Nika Layzell via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 1/1] reset: parse rev as tree-ish in patch mode
Date: Mon, 25 Nov 2019 10:58:51 +0900 [thread overview]
Message-ID: <xmqqblt0zpgk.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CACwGqKgPYMEHhfOnAEuCA3sNiuV0Wk_JQwU+c=vF7Wkhf=V9iQ@mail.gmail.com> (Nika Layzell's message of "Sun, 24 Nov 2019 13:31:06 -0500")
Nika Layzell <nika@thelayzells.com> writes:
>> Which means that perhaps a cleaner fix may be
>>
>> - if (unborn) {
>> + if (patch_mode) {
>> + /* do not compute or check &oid we will not use */
>> + ;
>> + } else if (unborn) {
>> ...
>>
>> right?
>
> I tried to make this change, however it has unfortunate side-effects. The
> "git-add--interactive" script does produce an error if it is not of the
> expected type, but it exits with a successful "0" status.
Thanks for being diligent. I love it when I see contributors do not
believe blindly what I suggest out of hunch and instead verify it
themselves.
> Given that the add--interactive script is undergoing a C rewrite, I am
> inclined to continue validating the argument in reset.c to avoid changes to
> the perl script.
Thanks. That is a very reasonable decision.
next prev parent reply other threads:[~2019-11-25 2:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 19:55 [PATCH 0/1] reset: parse rev as tree-ish in patch mode Nika Layzell via GitGitGadget
2019-11-23 19:55 ` [PATCH 1/1] " Nika Layzell via GitGitGadget
2019-11-24 5:54 ` Junio C Hamano
2019-11-24 18:31 ` Nika Layzell
2019-11-25 1:58 ` Junio C Hamano [this message]
2019-11-24 20:25 ` [PATCH v2 0/1] " Nika Layzell via GitGitGadget
2019-11-24 20:25 ` [PATCH v2 1/1] " Nika Layzell via GitGitGadget
2019-11-25 2:03 ` 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=xmqqblt0zpgk.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=nika@thelayzells.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).