From: Jonathan Nieder <jrnieder@gmail.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Sverre Rabbelier <srabbelier@gmail.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH] revert: add --stdin option to read commits from stdin
Date: Mon, 14 Jun 2010 00:20:27 -0500 [thread overview]
Message-ID: <20100614052027.GA1509@burratino> (raw)
In-Reply-To: <20100614032251.20121.83253.chriscool@tuxfamily.org>
Christian Couder wrote:
> --- a/t/t3508-cherry-pick-many-commits.sh
> +++ b/t/t3508-cherry-pick-many-commits.sh
> @@ -92,4 +92,14 @@ test_expect_failure 'cherry-pick -3 fourth works' '
> test "$(git rev-parse --verify HEAD)" != "$(git rev-parse --verify fourth)"
> '
>
> +test_expect_success 'cherry-pick --stdin works' '
> + git checkout master &&
> + git reset --hard first &&
[...]
This test fails for me as written, since the previous test leaves some
files in an unmerged state. Patch 1 below works around that.
> --- a/builtin/revert.c
> +++ b/builtin/revert.c
> @@ -79,7 +80,7 @@ static void parse_args(int argc, const char **argv)
> }
>
> commit_argc = parse_options(argc, argv, NULL, options, usage_str, 0);
[...]
> @@ -527,10 +528,12 @@ static void prepare_revs(struct rev_info *revs)
> {
> int argc = 0;
> int i;
> - const char **argv = xmalloc((commit_argc + 4) * sizeof(*argv));
> + const char **argv = xmalloc((commit_argc + 5) * sizeof(*argv));
>
> argv[argc++] = NULL;
> argv[argc++] = "--no-walk";
> + if (read_stdin)
> + argv[argc++] = "--stdin";
Ah, I see the problem now. But it would be even nicer to allow arbitrary
rev-list options, so a person could ‘git cherry-pick --reverse a..b’,
for example.
In other words, how about something like patch 2 below?
Patch 3 is a small cleanup, as a bonus.
Christian Couder (1):
revert: accept arbitrary rev-list options
Jonathan Nieder (2):
t3508 (cherry-pick): futureproof against unmerged files
revert: do not rebuild argv on heap
Documentation/git-cherry-pick.txt | 7 ++++++
builtin/revert.c | 37 ++++++++++++++++++-----------------
t/t3501-revert-cherry-pick.sh | 18 +++++++++++++++++
t/t3508-cherry-pick-many-commits.sh | 24 ++++++++++++++++------
4 files changed, 61 insertions(+), 25 deletions(-)
next prev parent reply other threads:[~2010-06-14 5:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 3:22 [PATCH] revert: add --stdin option to read commits from stdin Christian Couder
2010-06-14 5:20 ` Jonathan Nieder [this message]
2010-06-14 5:28 ` [PATCH 1/3] t3508 (cherry-pick): futureproof against unmerged files Jonathan Nieder
2010-06-14 5:29 ` [PATCH 2/3] revert: accept arbitrary rev-list options Jonathan Nieder
2010-06-14 5:32 ` [PATCH 3/3] revert: do not rebuild argv on heap Jonathan Nieder
2010-06-15 3:28 ` [PATCH] revert: add --stdin option to read commits from stdin Christian Couder
2010-06-14 6:20 ` Johannes Sixt
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=20100614052027.GA1509@burratino \
--to=jrnieder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=artagnon@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=srabbelier@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).