From: Neil Horman <nhorman@tuxdriver.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Phil Hord <phil.hord@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Neil Horman <nhorman@tuxdriver.com>
Subject: [PATCH v4 1/4] git-cherry-pick: add allow-empty option
Date: Wed, 11 Apr 2012 16:21:53 -0400 [thread overview]
Message-ID: <1334175716-11391-2-git-send-email-nhorman@tuxdriver.com> (raw)
In-Reply-To: <1334175716-11391-1-git-send-email-nhorman@tuxdriver.com>
git cherry-pick fails when picking a non-ff commit that is empty. The advice
given with the failure is that a git-commit --allow-empty should be issued to
explicitly add the empty commit during the cherry pick. This option allows a
user to specify before hand that they want to keep the empty commit. This
eliminates the need to issue both a cherry pick and a commit operation.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
---
Documentation/git-cherry-pick.txt | 9 +++++++++
builtin/revert.c | 2 ++
sequencer.c | 7 +++++--
sequencer.h | 1 +
4 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-cherry-pick.txt b/Documentation/git-cherry-pick.txt
index fed5097..730237a 100644
--- a/Documentation/git-cherry-pick.txt
+++ b/Documentation/git-cherry-pick.txt
@@ -103,6 +103,15 @@ effect to your index in a row.
cherry-pick'ed commit, then a fast forward to this commit will
be performed.
+--allow-empty::
+ By default, cherry-picking an empty commit will fail,
+ indicating that an explicit invocation of `git commit
+ --allow-empty` is required. This option overrides that
+ behavior, allowing empty commits to be preserved automatically
+ in a cherry-pick. Note that when "--ff" is in effect, empty
+ commits that meet the "fast-forward" requirement will be kept
+ even without this option.
+
--strategy=<strategy>::
Use the given merge strategy. Should only be used once.
See the MERGE STRATEGIES section in linkgit:git-merge[1]
diff --git a/builtin/revert.c b/builtin/revert.c
index e6840f2..06b00e6 100644
--- a/builtin/revert.c
+++ b/builtin/revert.c
@@ -114,12 +114,14 @@ static void parse_args(int argc, const char **argv, struct replay_opts *opts)
OPT_END(),
OPT_END(),
OPT_END(),
+ OPT_END(),
};
if (opts->action == REPLAY_PICK) {
struct option cp_extra[] = {
OPT_BOOLEAN('x', NULL, &opts->record_origin, "append commit name"),
OPT_BOOLEAN(0, "ff", &opts->allow_ff, "allow fast-forward"),
+ OPT_BOOLEAN(0, "allow-empty", &opts->allow_empty, "preserve empty commits"),
OPT_END(),
};
if (parse_options_concat(options, ARRAY_SIZE(options), cp_extra))
diff --git a/sequencer.c b/sequencer.c
index a37846a..71929ba 100644
--- a/sequencer.c
+++ b/sequencer.c
@@ -260,8 +260,8 @@ static int do_recursive_merge(struct commit *base, struct commit *next,
*/
static int run_git_commit(const char *defmsg, struct replay_opts *opts)
{
- /* 6 is max possible length of our args array including NULL */
- const char *args[6];
+ /* 7 is max possible length of our args array including NULL */
+ const char *args[7];
int i = 0;
args[i++] = "commit";
@@ -272,6 +272,9 @@ static int run_git_commit(const char *defmsg, struct replay_opts *opts)
args[i++] = "-F";
args[i++] = defmsg;
}
+ if (opts->allow_empty)
+ args[i++] = "--allow-empty";
+
args[i] = NULL;
return run_command_v_opt(args, RUN_GIT_CMD);
diff --git a/sequencer.h b/sequencer.h
index bb4b138..e2cd725 100644
--- a/sequencer.h
+++ b/sequencer.h
@@ -29,6 +29,7 @@ struct replay_opts {
int signoff;
int allow_ff;
int allow_rerere_auto;
+ int allow_empty;
int mainline;
--
1.7.7.6
next prev parent reply other threads:[~2012-04-11 20:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Enhance git-rebases flexibiilty in handling empty commits>
2012-04-11 20:21 ` [PATCH v4 0/4] Enhance git-rebases flexibiilty in handling empty commits Neil Horman
2012-04-11 20:21 ` Neil Horman [this message]
2012-04-11 20:21 ` [PATCH v4 2/4] git-cherry-pick: Add keep-redundant-commits option Neil Horman
2012-04-11 20:47 ` Junio C Hamano
2012-04-11 23:35 ` Neil Horman
2012-04-11 20:57 ` Junio C Hamano
2012-04-11 23:55 ` Neil Horman
2012-04-12 3:15 ` Junio C Hamano
2012-04-12 10:49 ` Neil Horman
2012-04-11 20:21 ` [PATCH v4 3/4] git-cherry-pick: Add test to validate new options Neil Horman
2012-04-11 21:06 ` Junio C Hamano
2012-04-11 20:21 ` [PATCH v4 4/4] git-rebase: add keep_empty flag Neil Horman
2012-04-11 21:08 ` Junio C Hamano
2012-04-11 23:59 ` Neil Horman
2012-04-12 3:16 ` Junio C Hamano
2012-04-12 15:58 ` Neil Horman
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=1334175716-11391-2-git-send-email-nhorman@tuxdriver.com \
--to=nhorman@tuxdriver.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=phil.hord@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).