From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Bryan Turner <bturner@atlassian.com>, Git Users <git@vger.kernel.org>
Subject: Re: Mismatched HEAD default behavior from git log
Date: Tue, 25 Aug 2020 12:51:59 -0700 [thread overview]
Message-ID: <xmqq4koq1p28.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200825194619.GB1419759@coredump.intra.peff.net> (Jeff King's message of "Tue, 25 Aug 2020 15:46:19 -0400")
Jeff King <peff@peff.net> writes:
>> As the intent for adding the "--stdin" option to any subcommand has
>> always been "we may need to feed many many things, that may bust the
>> command line length limit, hence we let you feed these things from
>> the standard input, but otherwise there should be no change in
>> behaviour or semantics", when the behaviour of command line and
>> "--stdin" differ, it is a bug in the latter.
>
> Agreed. It also helps in this case that the command-line behavior is
> sensible and the --stdin one is not. :)
>
> I think the solution is probably something like:
You beat me to it while I was wondering what to do between the local
got_rev_arg variable and the revs->rev_input_given field.
> diff --git a/revision.c b/revision.c
> index 96630e3186..f5bbefa091 100644
> --- a/revision.c
> +++ b/revision.c
> @@ -2099,12 +2099,13 @@ static void read_pathspec_from_stdin(struct strbuf *sb,
> strvec_push(prune, sb->buf);
> }
>
> -static void read_revisions_from_stdin(struct rev_info *revs,
> - struct strvec *prune)
> +static int read_revisions_from_stdin(struct rev_info *revs,
> + struct strvec *prune)
> {
> struct strbuf sb;
> int seen_dashdash = 0;
> int save_warning;
> + int got_rev_arg = 0;
>
> save_warning = warn_on_object_refname_ambiguity;
> warn_on_object_refname_ambiguity = 0;
> @@ -2124,12 +2125,14 @@ static void read_revisions_from_stdin(struct rev_info *revs,
> if (handle_revision_arg(sb.buf, revs, 0,
> REVARG_CANNOT_BE_FILENAME))
> die("bad revision '%s'", sb.buf);
> + got_rev_arg = 1;
> }
> if (seen_dashdash)
> read_pathspec_from_stdin(&sb, prune);
>
> strbuf_release(&sb);
> warn_on_object_refname_ambiguity = save_warning;
> + return got_rev_arg;
> }
>
> static void add_grep(struct rev_info *revs, const char *ptn, enum grep_pat_token what)
> @@ -2754,7 +2757,8 @@ int setup_revisions(int argc, const char **argv, struct rev_info *revs, struct s
> }
> if (revs->read_from_stdin++)
> die("--stdin given twice?");
> - read_revisions_from_stdin(revs, &prune_data);
> + if (read_revisions_from_stdin(revs, &prune_data))
> + got_rev_arg = 1;
> continue;
> }
>
>
> Possibly it would make sense to push that flag into rev_info, though,
> and let handle_revision_arg() set it. That would fix this bug and
> prevent similar ones in other code paths (though we're not likely to get
> revisions from anywhere else, I suppose).
>
> -Peff
next prev parent reply other threads:[~2020-08-25 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 19:16 Mismatched HEAD default behavior from git log Bryan Turner
2020-08-25 19:40 ` Junio C Hamano
2020-08-25 19:46 ` Jeff King
2020-08-25 19:51 ` Junio C Hamano [this message]
2020-08-25 19:55 ` Jeff King
2020-08-26 20:13 ` [PATCH] revision: set rev_input_given in handle_revision_arg() Jeff King
2020-08-26 20:20 ` 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=xmqq4koq1p28.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).