From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: Andrei Rybak <rybak.a.v@gmail.com>,
git@vger.kernel.org,
Christian Couder <christian.couder@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH v2 0/2] de-confuse git cherry-pick --author
Date: Wed, 11 Jul 2018 10:58:07 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1807111057500.75@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20180710043120.GA1330@sigill.intra.peff.net>
Hi Peff,
On Tue, 10 Jul 2018, Jeff King wrote:
> On Mon, Jul 09, 2018 at 10:15:05PM -0400, Jeff King wrote:
>
> > > Should this not rather be
> > >
> > > - if (!cmit || get_revision(opts->revs))
> > > - return error("BUG: expected exactly one commit from walk");
> > > + if (!cmit)
> > > + return error(_("empty commit set passed"));
> > > + if (get_revision(opts->revs))
> > > + return error(_("unexpected extra commit from walk"));
> >
> > Yeah, you're right. I'm not sure how a single rev with no-walk would
> > ever turn up more than one commit, though. So I think we should probably
> > go with:
> >
> > if (!cmit)
> > return error(_("empty commit set passed"));
> > if (get_revision(opts->revs))
> > BUG("unexpected extra commit from walk");
> >
> > And then if we ever see that case, we can decide from there what the
> > right action is (though _probably_ it's just to emit an error like you
> > have above, it might be a sign that our single-pick logic is wrong).
> >
> > I'll re-roll in that direction, and discuss further in the commit
> > message.
>
> After poking at it a bit more, I've convinced myself that this is the
> right thing, as options like "--branches" which expand into multiple
> tips already push us into the other code path.
>
> So here's a re-roll. The first one is identical except for the typo-fix
> in the commit message.
>
> [1/2]: sequencer: handle empty-set cases consistently
> [2/2]: sequencer: don't say BUG on bogus input
>
> sequencer.c | 12 ++++++++----
> t/t3510-cherry-pick-sequence.sh | 7 ++++++-
> 2 files changed, 14 insertions(+), 5 deletions(-)
ACK,
Dscho
next prev parent reply other threads:[~2018-07-11 8:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 14:16 [BUG] git cherry-pick does not complain about unknown options Andrei Rybak
2018-07-09 19:16 ` Jeff King
2018-07-09 19:46 ` [PATCH 0/2] de-confuse git cherry-pick --author behavior Jeff King
2018-07-09 19:48 ` [PATCH 1/2] sequencer: handle empty-set cases consistently Jeff King
2018-07-09 20:20 ` Junio C Hamano
2018-07-09 20:21 ` Johannes Schindelin
2018-07-09 19:49 ` [PATCH 2/2] sequencer: don't say BUG on bogus input Jeff King
2018-07-09 20:24 ` Johannes Schindelin
2018-07-09 21:11 ` Junio C Hamano
2018-07-10 2:15 ` Jeff King
2018-07-10 4:31 ` [PATCH v2 0/2] de-confuse git cherry-pick --author Jeff King
2018-07-10 4:31 ` [PATCH v2 1/2] sequencer: handle empty-set cases consistently Jeff King
2018-07-10 4:32 ` [PATCH v2 2/2] sequencer: don't say BUG on bogus input Jeff King
2018-07-11 8:58 ` Johannes Schindelin [this message]
2018-07-11 15:37 ` [PATCH v2 0/2] de-confuse git cherry-pick --author 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=nycvar.QRO.7.76.6.1807111057500.75@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=rybak.a.v@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.
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).