2011-08-04 12:39:11 +02:00
|
|
|
#include "cache.h"
|
2014-10-01 12:28:42 +02:00
|
|
|
#include "lockfile.h"
|
2011-08-04 12:39:11 +02:00
|
|
|
#include "sequencer.h"
|
|
|
|
#include "dir.h"
|
2012-01-11 19:15:57 +01:00
|
|
|
#include "object.h"
|
|
|
|
#include "commit.h"
|
|
|
|
#include "tag.h"
|
|
|
|
#include "run-command.h"
|
|
|
|
#include "exec_cmd.h"
|
|
|
|
#include "utf8.h"
|
|
|
|
#include "cache-tree.h"
|
|
|
|
#include "diff.h"
|
|
|
|
#include "revision.h"
|
|
|
|
#include "rerere.h"
|
|
|
|
#include "merge-recursive.h"
|
|
|
|
#include "refs.h"
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
#include "argv-array.h"
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
#define GIT_REFLOG_ACTION "GIT_REFLOG_ACTION"
|
2011-08-04 12:39:11 +02:00
|
|
|
|
2012-09-14 08:52:03 +02:00
|
|
|
const char sign_off_header[] = "Signed-off-by: ";
|
2013-02-12 11:17:32 +01:00
|
|
|
static const char cherry_picked_prefix[] = "(cherry picked from commit ";
|
2012-09-14 08:52:03 +02:00
|
|
|
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
static GIT_PATH_FUNC(git_path_todo_file, SEQ_TODO_FILE)
|
|
|
|
static GIT_PATH_FUNC(git_path_opts_file, SEQ_OPTS_FILE)
|
|
|
|
static GIT_PATH_FUNC(git_path_seq_dir, SEQ_DIR)
|
|
|
|
static GIT_PATH_FUNC(git_path_head_file, SEQ_HEAD_FILE)
|
|
|
|
|
2013-02-12 11:17:34 +01:00
|
|
|
static int is_rfc2822_line(const char *buf, int len)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < len; i++) {
|
|
|
|
int ch = buf[i];
|
|
|
|
if (ch == ':')
|
|
|
|
return 1;
|
|
|
|
if (!isalnum(ch) && ch != '-')
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int is_cherry_picked_from_line(const char *buf, int len)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* We only care that it looks roughly like (cherry picked from ...)
|
|
|
|
*/
|
|
|
|
return len > strlen(cherry_picked_prefix) + 1 &&
|
2013-11-30 21:55:40 +01:00
|
|
|
starts_with(buf, cherry_picked_prefix) && buf[len - 1] == ')';
|
2013-02-12 11:17:34 +01:00
|
|
|
}
|
|
|
|
|
2013-02-12 11:17:35 +01:00
|
|
|
/*
|
|
|
|
* Returns 0 for non-conforming footer
|
|
|
|
* Returns 1 for conforming footer
|
|
|
|
* Returns 2 when sob exists within conforming footer
|
|
|
|
* Returns 3 when sob exists within conforming footer as last entry
|
|
|
|
*/
|
|
|
|
static int has_conforming_footer(struct strbuf *sb, struct strbuf *sob,
|
|
|
|
int ignore_footer)
|
2013-02-12 11:17:34 +01:00
|
|
|
{
|
|
|
|
char prev;
|
|
|
|
int i, k;
|
|
|
|
int len = sb->len - ignore_footer;
|
|
|
|
const char *buf = sb->buf;
|
2013-02-12 11:17:35 +01:00
|
|
|
int found_sob = 0;
|
2013-02-12 11:17:34 +01:00
|
|
|
|
|
|
|
/* footer must end with newline */
|
|
|
|
if (!len || buf[len - 1] != '\n')
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
prev = '\0';
|
|
|
|
for (i = len - 1; i > 0; i--) {
|
|
|
|
char ch = buf[i];
|
|
|
|
if (prev == '\n' && ch == '\n') /* paragraph break */
|
|
|
|
break;
|
|
|
|
prev = ch;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* require at least one blank line */
|
|
|
|
if (prev != '\n' || buf[i] != '\n')
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
/* advance to start of last paragraph */
|
|
|
|
while (i < len - 1 && buf[i] == '\n')
|
|
|
|
i++;
|
|
|
|
|
|
|
|
for (; i < len; i = k) {
|
2013-02-12 11:17:35 +01:00
|
|
|
int found_rfc2822;
|
|
|
|
|
2013-02-12 11:17:34 +01:00
|
|
|
for (k = i; k < len && buf[k] != '\n'; k++)
|
|
|
|
; /* do nothing */
|
|
|
|
k++;
|
|
|
|
|
2013-02-12 11:17:35 +01:00
|
|
|
found_rfc2822 = is_rfc2822_line(buf + i, k - i - 1);
|
|
|
|
if (found_rfc2822 && sob &&
|
|
|
|
!strncmp(buf + i, sob->buf, sob->len))
|
|
|
|
found_sob = k;
|
|
|
|
|
|
|
|
if (!(found_rfc2822 ||
|
|
|
|
is_cherry_picked_from_line(buf + i, k - i - 1)))
|
2013-02-12 11:17:34 +01:00
|
|
|
return 0;
|
|
|
|
}
|
2013-02-12 11:17:35 +01:00
|
|
|
if (found_sob == i)
|
|
|
|
return 3;
|
|
|
|
if (found_sob)
|
|
|
|
return 2;
|
2013-02-12 11:17:34 +01:00
|
|
|
return 1;
|
|
|
|
}
|
2012-09-14 08:52:03 +02:00
|
|
|
|
2012-09-16 08:20:40 +02:00
|
|
|
static void remove_sequencer_state(void)
|
2011-08-04 12:39:11 +02:00
|
|
|
{
|
|
|
|
struct strbuf seq_dir = STRBUF_INIT;
|
|
|
|
|
|
|
|
strbuf_addf(&seq_dir, "%s", git_path(SEQ_DIR));
|
2011-12-10 14:06:12 +01:00
|
|
|
remove_dir_recursively(&seq_dir, 0);
|
2011-08-04 12:39:11 +02:00
|
|
|
strbuf_release(&seq_dir);
|
|
|
|
}
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
static const char *action_name(const struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
return opts->action == REPLAY_REVERT ? "revert" : "cherry-pick";
|
|
|
|
}
|
|
|
|
|
|
|
|
struct commit_message {
|
|
|
|
char *parent_label;
|
2016-02-22 23:44:57 +01:00
|
|
|
char *label;
|
|
|
|
char *subject;
|
2012-01-11 19:15:57 +01:00
|
|
|
const char *message;
|
|
|
|
};
|
|
|
|
|
|
|
|
static int get_message(struct commit *commit, struct commit_message *out)
|
|
|
|
{
|
|
|
|
const char *abbrev, *subject;
|
2016-02-22 23:44:57 +01:00
|
|
|
int subject_len;
|
2012-01-11 19:15:57 +01:00
|
|
|
|
2016-02-22 23:44:57 +01:00
|
|
|
out->message = logmsg_reencode(commit, NULL, get_commit_output_encoding());
|
2015-11-10 03:22:28 +01:00
|
|
|
abbrev = find_unique_abbrev(commit->object.oid.hash, DEFAULT_ABBREV);
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
subject_len = find_commit_subject(out->message, &subject);
|
|
|
|
|
2016-02-22 23:44:57 +01:00
|
|
|
out->subject = xmemdupz(subject, subject_len);
|
|
|
|
out->label = xstrfmt("%s... %s", abbrev, out->subject);
|
|
|
|
out->parent_label = xstrfmt("parent of %s", out->label);
|
|
|
|
|
2012-01-11 19:15:57 +01:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2014-06-10 23:39:35 +02:00
|
|
|
static void free_message(struct commit *commit, struct commit_message *msg)
|
2012-01-11 19:15:57 +01:00
|
|
|
{
|
|
|
|
free(msg->parent_label);
|
2016-02-22 23:44:57 +01:00
|
|
|
free(msg->label);
|
|
|
|
free(msg->subject);
|
2014-06-10 23:41:39 +02:00
|
|
|
unuse_commit_buffer(commit, msg->message);
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
|
2012-02-22 01:44:17 +01:00
|
|
|
static void print_advice(int show_hint, struct replay_opts *opts)
|
2012-01-11 19:15:57 +01:00
|
|
|
{
|
|
|
|
char *msg = getenv("GIT_CHERRY_PICK_HELP");
|
|
|
|
|
|
|
|
if (msg) {
|
|
|
|
fprintf(stderr, "%s\n", msg);
|
|
|
|
/*
|
2013-04-12 00:36:10 +02:00
|
|
|
* A conflict has occurred but the porcelain
|
2012-01-11 19:15:57 +01:00
|
|
|
* (typically rebase --interactive) wants to take care
|
|
|
|
* of the commit itself so remove CHERRY_PICK_HEAD
|
|
|
|
*/
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
unlink(git_path_cherry_pick_head());
|
2012-01-11 19:15:57 +01:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2012-02-22 01:44:17 +01:00
|
|
|
if (show_hint) {
|
|
|
|
if (opts->no_commit)
|
|
|
|
advise(_("after resolving the conflicts, mark the corrected paths\n"
|
|
|
|
"with 'git add <paths>' or 'git rm <paths>'"));
|
|
|
|
else
|
|
|
|
advise(_("after resolving the conflicts, mark the corrected paths\n"
|
|
|
|
"with 'git add <paths>' or 'git rm <paths>'\n"
|
|
|
|
"and commit the result with 'git commit'"));
|
|
|
|
}
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
static void write_message(struct strbuf *msgbuf, const char *filename)
|
|
|
|
{
|
|
|
|
static struct lock_file msg_file;
|
|
|
|
|
|
|
|
int msg_fd = hold_lock_file_for_update(&msg_file, filename,
|
|
|
|
LOCK_DIE_ON_ERROR);
|
|
|
|
if (write_in_full(msg_fd, msgbuf->buf, msgbuf->len) < 0)
|
|
|
|
die_errno(_("Could not write to %s"), filename);
|
|
|
|
strbuf_release(msgbuf);
|
|
|
|
if (commit_lock_file(&msg_file) < 0)
|
|
|
|
die(_("Error wrapping up %s"), filename);
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct tree *empty_tree(void)
|
|
|
|
{
|
2012-03-22 19:53:24 +01:00
|
|
|
return lookup_tree(EMPTY_TREE_SHA1_BIN);
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
static int error_dirty_index(struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
if (read_cache_unmerged())
|
|
|
|
return error_resolve_conflict(action_name(opts));
|
|
|
|
|
|
|
|
/* Different translation strings for cherry-pick and revert */
|
|
|
|
if (opts->action == REPLAY_PICK)
|
|
|
|
error(_("Your local changes would be overwritten by cherry-pick."));
|
|
|
|
else
|
|
|
|
error(_("Your local changes would be overwritten by revert."));
|
|
|
|
|
|
|
|
if (advice_commit_before_merge)
|
|
|
|
advise(_("Commit your changes or stash them to proceed."));
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2012-12-21 20:10:11 +01:00
|
|
|
static int fast_forward_to(const unsigned char *to, const unsigned char *from,
|
2013-06-19 09:37:09 +02:00
|
|
|
int unborn, struct replay_opts *opts)
|
2012-01-11 19:15:57 +01:00
|
|
|
{
|
2014-04-17 00:37:45 +02:00
|
|
|
struct ref_transaction *transaction;
|
2013-06-19 09:37:09 +02:00
|
|
|
struct strbuf sb = STRBUF_INIT;
|
2014-04-17 00:37:45 +02:00
|
|
|
struct strbuf err = STRBUF_INIT;
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
read_cache();
|
2012-10-26 17:53:49 +02:00
|
|
|
if (checkout_fast_forward(from, to, 1))
|
2014-06-09 17:04:36 +02:00
|
|
|
exit(128); /* the callee should have complained already */
|
2014-04-16 20:56:52 +02:00
|
|
|
|
2013-06-19 09:37:09 +02:00
|
|
|
strbuf_addf(&sb, "%s: fast-forward", action_name(opts));
|
2014-04-17 00:37:45 +02:00
|
|
|
|
|
|
|
transaction = ref_transaction_begin(&err);
|
|
|
|
if (!transaction ||
|
|
|
|
ref_transaction_update(transaction, "HEAD",
|
|
|
|
to, unborn ? null_sha1 : from,
|
2015-02-17 18:00:15 +01:00
|
|
|
0, sb.buf, &err) ||
|
2014-04-30 21:22:42 +02:00
|
|
|
ref_transaction_commit(transaction, &err)) {
|
2014-04-17 00:37:45 +02:00
|
|
|
ref_transaction_free(transaction);
|
|
|
|
error("%s", err.buf);
|
|
|
|
strbuf_release(&sb);
|
|
|
|
strbuf_release(&err);
|
|
|
|
return -1;
|
|
|
|
}
|
2014-04-16 20:56:52 +02:00
|
|
|
|
2013-06-19 09:37:09 +02:00
|
|
|
strbuf_release(&sb);
|
2014-04-17 00:37:45 +02:00
|
|
|
strbuf_release(&err);
|
|
|
|
ref_transaction_free(transaction);
|
|
|
|
return 0;
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
|
2014-10-24 20:34:59 +02:00
|
|
|
void append_conflicts_hint(struct strbuf *msgbuf)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
2014-10-28 21:04:38 +01:00
|
|
|
strbuf_addch(msgbuf, '\n');
|
|
|
|
strbuf_commented_addf(msgbuf, "Conflicts:\n");
|
2014-10-24 20:34:59 +02:00
|
|
|
for (i = 0; i < active_nr;) {
|
|
|
|
const struct cache_entry *ce = active_cache[i++];
|
|
|
|
if (ce_stage(ce)) {
|
2014-10-28 21:04:38 +01:00
|
|
|
strbuf_commented_addf(msgbuf, "\t%s\n", ce->name);
|
2014-10-24 20:34:59 +02:00
|
|
|
while (i < active_nr && !strcmp(ce->name,
|
|
|
|
active_cache[i]->name))
|
|
|
|
i++;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2012-01-11 19:15:57 +01:00
|
|
|
static int do_recursive_merge(struct commit *base, struct commit *next,
|
|
|
|
const char *base_label, const char *next_label,
|
|
|
|
unsigned char *head, struct strbuf *msgbuf,
|
|
|
|
struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
struct merge_options o;
|
|
|
|
struct tree *result, *next_tree, *base_tree, *head_tree;
|
2014-06-13 14:19:23 +02:00
|
|
|
int clean;
|
2012-01-11 19:15:57 +01:00
|
|
|
const char **xopt;
|
|
|
|
static struct lock_file index_lock;
|
|
|
|
|
2014-06-13 14:19:23 +02:00
|
|
|
hold_locked_index(&index_lock, 1);
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
read_cache();
|
|
|
|
|
|
|
|
init_merge_options(&o);
|
|
|
|
o.ancestor = base ? base_label : "(empty tree)";
|
|
|
|
o.branch1 = "HEAD";
|
|
|
|
o.branch2 = next ? next_label : "(empty tree)";
|
|
|
|
|
|
|
|
head_tree = parse_tree_indirect(head);
|
|
|
|
next_tree = next ? next->tree : empty_tree();
|
|
|
|
base_tree = base ? base->tree : empty_tree();
|
|
|
|
|
|
|
|
for (xopt = opts->xopts; xopt != opts->xopts + opts->xopts_nr; xopt++)
|
|
|
|
parse_merge_opt(&o, *xopt);
|
|
|
|
|
|
|
|
clean = merge_trees(&o,
|
|
|
|
head_tree,
|
|
|
|
next_tree, base_tree, &result);
|
|
|
|
|
|
|
|
if (active_cache_changed &&
|
2014-06-13 14:19:23 +02:00
|
|
|
write_locked_index(&the_index, &index_lock, COMMIT_LOCK))
|
2012-01-11 19:15:57 +01:00
|
|
|
/* TRANSLATORS: %s will be "revert" or "cherry-pick" */
|
|
|
|
die(_("%s: Unable to write new index file"), action_name(opts));
|
|
|
|
rollback_lock_file(&index_lock);
|
|
|
|
|
2012-09-14 08:52:03 +02:00
|
|
|
if (opts->signoff)
|
2013-02-12 11:17:35 +01:00
|
|
|
append_signoff(msgbuf, 0, 0);
|
2012-09-14 08:52:03 +02:00
|
|
|
|
2014-10-24 20:34:59 +02:00
|
|
|
if (!clean)
|
|
|
|
append_conflicts_hint(msgbuf);
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
return !clean;
|
|
|
|
}
|
|
|
|
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
static int is_index_unchanged(void)
|
|
|
|
{
|
|
|
|
unsigned char head_sha1[20];
|
|
|
|
struct commit *head_commit;
|
|
|
|
|
2014-07-15 21:59:36 +02:00
|
|
|
if (!resolve_ref_unsafe("HEAD", RESOLVE_REF_READING, head_sha1, NULL))
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
return error(_("Could not resolve HEAD commit\n"));
|
|
|
|
|
|
|
|
head_commit = lookup_commit(head_sha1);
|
2012-05-03 14:10:22 +02:00
|
|
|
|
|
|
|
/*
|
|
|
|
* If head_commit is NULL, check_commit, called from
|
|
|
|
* lookup_commit, would have indicated that head_commit is not
|
|
|
|
* a commit object already. parse_commit() will return failure
|
|
|
|
* without further complaints in such a case. Otherwise, if
|
|
|
|
* the commit is invalid, parse_commit() will complain. So
|
|
|
|
* there is nothing for us to say here. Just return failure.
|
|
|
|
*/
|
|
|
|
if (parse_commit(head_commit))
|
|
|
|
return -1;
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
|
|
|
|
if (!active_cache_tree)
|
|
|
|
active_cache_tree = cache_tree();
|
|
|
|
|
|
|
|
if (!cache_tree_fully_valid(active_cache_tree))
|
2014-06-13 14:19:32 +02:00
|
|
|
if (cache_tree_update(&the_index, 0))
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
return error(_("Unable to update cache tree\n"));
|
|
|
|
|
2015-11-10 03:22:29 +01:00
|
|
|
return !hashcmp(active_cache_tree->sha1, head_commit->tree->object.oid.hash);
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
}
|
|
|
|
|
2012-01-11 19:15:57 +01:00
|
|
|
/*
|
|
|
|
* If we are cherry-pick, and if the merge did not result in
|
|
|
|
* hand-editing, we will hit this commit and inherit the original
|
|
|
|
* author date and name.
|
|
|
|
* If we are revert, or if our cherry-pick results in a hand merge,
|
|
|
|
* we had better say that the current user is responsible for that.
|
|
|
|
*/
|
2012-05-30 02:14:41 +02:00
|
|
|
static int run_git_commit(const char *defmsg, struct replay_opts *opts,
|
|
|
|
int allow_empty)
|
2012-01-11 19:15:57 +01:00
|
|
|
{
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
struct argv_array array;
|
|
|
|
int rc;
|
2015-03-06 14:55:32 +01:00
|
|
|
const char *value;
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
|
|
|
|
argv_array_init(&array);
|
|
|
|
argv_array_push(&array, "commit");
|
|
|
|
argv_array_push(&array, "-n");
|
2012-01-11 19:15:57 +01:00
|
|
|
|
2014-06-19 23:28:20 +02:00
|
|
|
if (opts->gpg_sign)
|
|
|
|
argv_array_pushf(&array, "-S%s", opts->gpg_sign);
|
2012-01-11 19:15:57 +01:00
|
|
|
if (opts->signoff)
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
argv_array_push(&array, "-s");
|
2012-01-11 19:15:57 +01:00
|
|
|
if (!opts->edit) {
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
argv_array_push(&array, "-F");
|
|
|
|
argv_array_push(&array, defmsg);
|
2015-03-06 14:55:32 +01:00
|
|
|
if (!opts->signoff &&
|
|
|
|
!opts->record_origin &&
|
|
|
|
git_config_get_value("commit.cleanup", &value))
|
|
|
|
argv_array_push(&array, "--cleanup=verbatim");
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
|
2012-05-30 02:14:41 +02:00
|
|
|
if (allow_empty)
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
argv_array_push(&array, "--allow-empty");
|
2012-04-11 22:21:53 +02:00
|
|
|
|
2012-08-02 12:38:51 +02:00
|
|
|
if (opts->allow_empty_message)
|
|
|
|
argv_array_push(&array, "--allow-empty-message");
|
|
|
|
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
rc = run_command_v_opt(array.argv, RUN_GIT_CMD);
|
|
|
|
argv_array_clear(&array);
|
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int is_original_commit_empty(struct commit *commit)
|
|
|
|
{
|
|
|
|
const unsigned char *ptree_sha1;
|
|
|
|
|
|
|
|
if (parse_commit(commit))
|
|
|
|
return error(_("Could not parse commit %s\n"),
|
2015-11-10 03:22:28 +01:00
|
|
|
oid_to_hex(&commit->object.oid));
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
if (commit->parents) {
|
|
|
|
struct commit *parent = commit->parents->item;
|
|
|
|
if (parse_commit(parent))
|
|
|
|
return error(_("Could not parse parent commit %s\n"),
|
2015-11-10 03:22:28 +01:00
|
|
|
oid_to_hex(&parent->object.oid));
|
2015-11-10 03:22:29 +01:00
|
|
|
ptree_sha1 = parent->tree->object.oid.hash;
|
git-cherry-pick: Add keep-redundant-commits option
The git-cherry-pick --allow-empty command by default only preserves empty
commits that were originally empty, i.e only those commits for which
<commit>^{tree} and <commit>^^{tree} are equal. By default commits which are
non-empty, but were made empty by the inclusion of a prior commit on the current
history are filtered out. This option allows us to override that behavior and
include redundant commits as empty commits in the change history.
Note that this patch changes the default behavior of git cherry-pick slightly.
Prior to this patch all commits in a cherry-pick sequence were applied and git
commit was run. The implication here was that, if a commit was redundant, and
the commit did not trigger the fast forward logic, the git commit operation, and
therefore the git cherry-pick operation would fail, displaying the cherry pick
advice (i.e. run git commit --allow-empty). With this patch however, such
redundant commits are automatically skipped without stopping, unless
--keep-redundant-commits is specified, in which case, they are automatically
applied as empty commits.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-20 16:36:15 +02:00
|
|
|
} else {
|
|
|
|
ptree_sha1 = EMPTY_TREE_SHA1_BIN; /* commit is root */
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
|
2015-11-10 03:22:29 +01:00
|
|
|
return !hashcmp(ptree_sha1, commit->tree->object.oid.hash);
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
|
2012-05-30 02:14:41 +02:00
|
|
|
/*
|
|
|
|
* Do we run "git commit" with "--allow-empty"?
|
|
|
|
*/
|
|
|
|
static int allow_empty(struct replay_opts *opts, struct commit *commit)
|
|
|
|
{
|
|
|
|
int index_unchanged, empty_commit;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Three cases:
|
|
|
|
*
|
|
|
|
* (1) we do not allow empty at all and error out.
|
|
|
|
*
|
|
|
|
* (2) we allow ones that were initially empty, but
|
|
|
|
* forbid the ones that become empty;
|
|
|
|
*
|
|
|
|
* (3) we allow both.
|
|
|
|
*/
|
|
|
|
if (!opts->allow_empty)
|
|
|
|
return 0; /* let "git commit" barf as necessary */
|
|
|
|
|
|
|
|
index_unchanged = is_index_unchanged();
|
|
|
|
if (index_unchanged < 0)
|
|
|
|
return index_unchanged;
|
|
|
|
if (!index_unchanged)
|
|
|
|
return 0; /* we do not have to say --allow-empty */
|
|
|
|
|
|
|
|
if (opts->keep_redundant_commits)
|
|
|
|
return 1;
|
|
|
|
|
|
|
|
empty_commit = is_original_commit_empty(commit);
|
|
|
|
if (empty_commit < 0)
|
|
|
|
return empty_commit;
|
|
|
|
if (!empty_commit)
|
|
|
|
return 0;
|
|
|
|
else
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2012-01-11 19:15:57 +01:00
|
|
|
static int do_pick_commit(struct commit *commit, struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
unsigned char head[20];
|
|
|
|
struct commit *base, *next, *parent;
|
|
|
|
const char *base_label, *next_label;
|
2014-06-10 23:39:35 +02:00
|
|
|
struct commit_message msg = { NULL, NULL, NULL, NULL };
|
2012-01-11 19:15:57 +01:00
|
|
|
struct strbuf msgbuf = STRBUF_INIT;
|
2013-05-29 05:56:21 +02:00
|
|
|
int res, unborn = 0, allow;
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
if (opts->no_commit) {
|
|
|
|
/*
|
|
|
|
* We do not intend to commit immediately. We just want to
|
|
|
|
* merge the differences in, so let's compute the tree
|
|
|
|
* that represents the "current" state for merge-recursive
|
|
|
|
* to work on.
|
|
|
|
*/
|
|
|
|
if (write_cache_as_tree(head, 0, NULL))
|
|
|
|
die (_("Your index file is unmerged."));
|
|
|
|
} else {
|
2012-12-21 20:10:11 +01:00
|
|
|
unborn = get_sha1("HEAD", head);
|
|
|
|
if (unborn)
|
|
|
|
hashcpy(head, EMPTY_TREE_SHA1_BIN);
|
|
|
|
if (index_differs_from(unborn ? EMPTY_TREE_SHA1_HEX : "HEAD", 0))
|
2012-01-11 19:15:57 +01:00
|
|
|
return error_dirty_index(opts);
|
|
|
|
}
|
|
|
|
discard_cache();
|
|
|
|
|
|
|
|
if (!commit->parents) {
|
|
|
|
parent = NULL;
|
|
|
|
}
|
|
|
|
else if (commit->parents->next) {
|
|
|
|
/* Reverting or cherry-picking a merge commit */
|
|
|
|
int cnt;
|
|
|
|
struct commit_list *p;
|
|
|
|
|
|
|
|
if (!opts->mainline)
|
|
|
|
return error(_("Commit %s is a merge but no -m option was given."),
|
2015-11-10 03:22:28 +01:00
|
|
|
oid_to_hex(&commit->object.oid));
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
for (cnt = 1, p = commit->parents;
|
|
|
|
cnt != opts->mainline && p;
|
|
|
|
cnt++)
|
|
|
|
p = p->next;
|
|
|
|
if (cnt != opts->mainline || !p)
|
|
|
|
return error(_("Commit %s does not have parent %d"),
|
2015-11-10 03:22:28 +01:00
|
|
|
oid_to_hex(&commit->object.oid), opts->mainline);
|
2012-01-11 19:15:57 +01:00
|
|
|
parent = p->item;
|
|
|
|
} else if (0 < opts->mainline)
|
|
|
|
return error(_("Mainline was specified but commit %s is not a merge."),
|
2015-11-10 03:22:28 +01:00
|
|
|
oid_to_hex(&commit->object.oid));
|
2012-01-11 19:15:57 +01:00
|
|
|
else
|
|
|
|
parent = commit->parents->item;
|
|
|
|
|
2012-12-21 20:10:11 +01:00
|
|
|
if (opts->allow_ff &&
|
2015-11-10 03:22:29 +01:00
|
|
|
((parent && !hashcmp(parent->object.oid.hash, head)) ||
|
2012-12-21 20:10:11 +01:00
|
|
|
(!parent && unborn)))
|
2015-11-10 03:22:29 +01:00
|
|
|
return fast_forward_to(commit->object.oid.hash, head, unborn, opts);
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
if (parent && parse_commit(parent) < 0)
|
|
|
|
/* TRANSLATORS: The first %s will be "revert" or
|
|
|
|
"cherry-pick", the second %s a SHA1 */
|
|
|
|
return error(_("%s: cannot parse parent commit %s"),
|
2015-11-10 03:22:28 +01:00
|
|
|
action_name(opts), oid_to_hex(&parent->object.oid));
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
if (get_message(commit, &msg) != 0)
|
|
|
|
return error(_("Cannot get commit message for %s"),
|
2015-11-10 03:22:28 +01:00
|
|
|
oid_to_hex(&commit->object.oid));
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
/*
|
|
|
|
* "commit" is an existing commit. We would want to apply
|
|
|
|
* the difference it introduces since its first parent "prev"
|
|
|
|
* on top of the current HEAD if we are cherry-pick. Or the
|
|
|
|
* reverse of it if we are revert.
|
|
|
|
*/
|
|
|
|
|
|
|
|
if (opts->action == REPLAY_REVERT) {
|
|
|
|
base = commit;
|
|
|
|
base_label = msg.label;
|
|
|
|
next = parent;
|
|
|
|
next_label = msg.parent_label;
|
|
|
|
strbuf_addstr(&msgbuf, "Revert \"");
|
|
|
|
strbuf_addstr(&msgbuf, msg.subject);
|
|
|
|
strbuf_addstr(&msgbuf, "\"\n\nThis reverts commit ");
|
2015-11-10 03:22:28 +01:00
|
|
|
strbuf_addstr(&msgbuf, oid_to_hex(&commit->object.oid));
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
if (commit->parents && commit->parents->next) {
|
|
|
|
strbuf_addstr(&msgbuf, ", reversing\nchanges made to ");
|
2015-11-10 03:22:28 +01:00
|
|
|
strbuf_addstr(&msgbuf, oid_to_hex(&parent->object.oid));
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
strbuf_addstr(&msgbuf, ".\n");
|
|
|
|
} else {
|
|
|
|
const char *p;
|
|
|
|
|
|
|
|
base = parent;
|
|
|
|
base_label = msg.parent_label;
|
|
|
|
next = commit;
|
|
|
|
next_label = msg.label;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Append the commit log message to msgbuf; it starts
|
|
|
|
* after the tree, parent, author, committer
|
|
|
|
* information followed by "\n\n".
|
|
|
|
*/
|
|
|
|
p = strstr(msg.message, "\n\n");
|
2016-06-29 16:14:46 +02:00
|
|
|
if (p)
|
|
|
|
strbuf_addstr(&msgbuf, skip_blank_lines(p + 2));
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
if (opts->record_origin) {
|
2013-02-12 11:17:35 +01:00
|
|
|
if (!has_conforming_footer(&msgbuf, NULL, 0))
|
2013-02-12 11:17:34 +01:00
|
|
|
strbuf_addch(&msgbuf, '\n');
|
2013-02-12 11:17:32 +01:00
|
|
|
strbuf_addstr(&msgbuf, cherry_picked_prefix);
|
2015-11-10 03:22:28 +01:00
|
|
|
strbuf_addstr(&msgbuf, oid_to_hex(&commit->object.oid));
|
2012-01-11 19:15:57 +01:00
|
|
|
strbuf_addstr(&msgbuf, ")\n");
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!opts->strategy || !strcmp(opts->strategy, "recursive") || opts->action == REPLAY_REVERT) {
|
|
|
|
res = do_recursive_merge(base, next, base_label, next_label,
|
|
|
|
head, &msgbuf, opts);
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
write_message(&msgbuf, git_path_merge_msg());
|
2012-01-11 19:15:57 +01:00
|
|
|
} else {
|
|
|
|
struct commit_list *common = NULL;
|
|
|
|
struct commit_list *remotes = NULL;
|
|
|
|
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
write_message(&msgbuf, git_path_merge_msg());
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
commit_list_insert(base, &common);
|
|
|
|
commit_list_insert(next, &remotes);
|
|
|
|
res = try_merge_command(opts->strategy, opts->xopts_nr, opts->xopts,
|
|
|
|
common, sha1_to_hex(head), remotes);
|
|
|
|
free_commit_list(common);
|
|
|
|
free_commit_list(remotes);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If the merge was clean or if it failed due to conflict, we write
|
|
|
|
* CHERRY_PICK_HEAD for the subsequent invocation of commit to use.
|
|
|
|
* However, if the merge did not even start, then we don't want to
|
|
|
|
* write it at all.
|
|
|
|
*/
|
|
|
|
if (opts->action == REPLAY_PICK && !opts->no_commit && (res == 0 || res == 1))
|
2015-11-10 03:22:29 +01:00
|
|
|
update_ref(NULL, "CHERRY_PICK_HEAD", commit->object.oid.hash, NULL,
|
2015-07-31 08:06:21 +02:00
|
|
|
REF_NODEREF, UPDATE_REFS_DIE_ON_ERR);
|
2012-01-11 19:15:57 +01:00
|
|
|
if (opts->action == REPLAY_REVERT && ((opts->no_commit && res == 0) || res == 1))
|
2015-11-10 03:22:29 +01:00
|
|
|
update_ref(NULL, "REVERT_HEAD", commit->object.oid.hash, NULL,
|
2015-07-31 08:06:21 +02:00
|
|
|
REF_NODEREF, UPDATE_REFS_DIE_ON_ERR);
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
if (res) {
|
|
|
|
error(opts->action == REPLAY_REVERT
|
|
|
|
? _("could not revert %s... %s")
|
|
|
|
: _("could not apply %s... %s"),
|
2015-11-10 03:22:29 +01:00
|
|
|
find_unique_abbrev(commit->object.oid.hash, DEFAULT_ABBREV),
|
2012-01-11 19:15:57 +01:00
|
|
|
msg.subject);
|
2012-02-22 01:44:17 +01:00
|
|
|
print_advice(res == 1, opts);
|
2012-01-11 19:15:57 +01:00
|
|
|
rerere(opts->allow_rerere_auto);
|
2013-05-29 05:56:21 +02:00
|
|
|
goto leave;
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
|
2013-05-29 05:56:21 +02:00
|
|
|
allow = allow_empty(opts, commit);
|
2013-06-06 10:58:57 +02:00
|
|
|
if (allow < 0) {
|
|
|
|
res = allow;
|
|
|
|
goto leave;
|
|
|
|
}
|
2013-05-29 05:56:21 +02:00
|
|
|
if (!opts->no_commit)
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
res = run_git_commit(git_path_merge_msg(), opts, allow);
|
2013-05-29 05:56:21 +02:00
|
|
|
|
|
|
|
leave:
|
2014-06-10 23:39:35 +02:00
|
|
|
free_message(commit, &msg);
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
return res;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void prepare_revs(struct replay_opts *opts)
|
|
|
|
{
|
2012-08-29 08:15:56 +02:00
|
|
|
/*
|
|
|
|
* picking (but not reverting) ranges (but not individual revisions)
|
|
|
|
* should be done in reverse
|
|
|
|
*/
|
|
|
|
if (opts->action == REPLAY_PICK && !opts->revs->no_walk)
|
2012-01-11 19:15:57 +01:00
|
|
|
opts->revs->reverse ^= 1;
|
|
|
|
|
|
|
|
if (prepare_revision_walk(opts->revs))
|
|
|
|
die(_("revision walk setup failed"));
|
|
|
|
|
|
|
|
if (!opts->revs->commits)
|
|
|
|
die(_("empty commit set passed"));
|
|
|
|
}
|
|
|
|
|
|
|
|
static void read_and_refresh_cache(struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
static struct lock_file index_lock;
|
|
|
|
int index_fd = hold_locked_index(&index_lock, 0);
|
|
|
|
if (read_index_preload(&the_index, NULL) < 0)
|
|
|
|
die(_("git %s: failed to read the index"), action_name(opts));
|
|
|
|
refresh_index(&the_index, REFRESH_QUIET|REFRESH_UNMERGED, NULL, NULL, NULL);
|
2014-04-28 12:55:24 +02:00
|
|
|
if (the_index.cache_changed && index_fd >= 0) {
|
2014-06-13 14:19:23 +02:00
|
|
|
if (write_locked_index(&the_index, &index_lock, COMMIT_LOCK))
|
2012-01-11 19:15:57 +01:00
|
|
|
die(_("git %s: failed to refresh the index"), action_name(opts));
|
|
|
|
}
|
|
|
|
rollback_lock_file(&index_lock);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int format_todo(struct strbuf *buf, struct commit_list *todo_list,
|
|
|
|
struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
struct commit_list *cur = NULL;
|
|
|
|
const char *sha1_abbrev = NULL;
|
|
|
|
const char *action_str = opts->action == REPLAY_REVERT ? "revert" : "pick";
|
|
|
|
const char *subject;
|
|
|
|
int subject_len;
|
|
|
|
|
|
|
|
for (cur = todo_list; cur; cur = cur->next) {
|
2014-06-10 23:44:13 +02:00
|
|
|
const char *commit_buffer = get_commit_buffer(cur->item, NULL);
|
2015-11-10 03:22:29 +01:00
|
|
|
sha1_abbrev = find_unique_abbrev(cur->item->object.oid.hash, DEFAULT_ABBREV);
|
2014-06-10 23:41:51 +02:00
|
|
|
subject_len = find_commit_subject(commit_buffer, &subject);
|
2012-01-11 19:15:57 +01:00
|
|
|
strbuf_addf(buf, "%s %s %.*s\n", action_str, sha1_abbrev,
|
|
|
|
subject_len, subject);
|
2014-06-10 23:41:51 +02:00
|
|
|
unuse_commit_buffer(cur->item, commit_buffer);
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct commit *parse_insn_line(char *bol, char *eol, struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
unsigned char commit_sha1[20];
|
|
|
|
enum replay_action action;
|
|
|
|
char *end_of_object_name;
|
|
|
|
int saved, status, padding;
|
|
|
|
|
2013-11-30 21:55:40 +01:00
|
|
|
if (starts_with(bol, "pick")) {
|
2012-01-11 19:15:57 +01:00
|
|
|
action = REPLAY_PICK;
|
|
|
|
bol += strlen("pick");
|
2013-11-30 21:55:40 +01:00
|
|
|
} else if (starts_with(bol, "revert")) {
|
2012-01-11 19:15:57 +01:00
|
|
|
action = REPLAY_REVERT;
|
|
|
|
bol += strlen("revert");
|
|
|
|
} else
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
/* Eat up extra spaces/ tabs before object name */
|
|
|
|
padding = strspn(bol, " \t");
|
|
|
|
if (!padding)
|
|
|
|
return NULL;
|
|
|
|
bol += padding;
|
|
|
|
|
|
|
|
end_of_object_name = bol + strcspn(bol, " \t\n");
|
|
|
|
saved = *end_of_object_name;
|
|
|
|
*end_of_object_name = '\0';
|
|
|
|
status = get_sha1(bol, commit_sha1);
|
|
|
|
*end_of_object_name = saved;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Verify that the action matches up with the one in
|
|
|
|
* opts; we don't support arbitrary instructions
|
|
|
|
*/
|
|
|
|
if (action != opts->action) {
|
|
|
|
const char *action_str;
|
|
|
|
action_str = action == REPLAY_REVERT ? "revert" : "cherry-pick";
|
|
|
|
error(_("Cannot %s during a %s"), action_str, action_name(opts));
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (status < 0)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
return lookup_commit_reference(commit_sha1);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int parse_insn_buffer(char *buf, struct commit_list **todo_list,
|
|
|
|
struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
struct commit_list **next = todo_list;
|
|
|
|
struct commit *commit;
|
|
|
|
char *p = buf;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 1; *p; i++) {
|
|
|
|
char *eol = strchrnul(p, '\n');
|
|
|
|
commit = parse_insn_line(p, eol, opts);
|
|
|
|
if (!commit)
|
|
|
|
return error(_("Could not parse line %d."), i);
|
|
|
|
next = commit_list_append(commit, next);
|
|
|
|
p = *eol ? eol + 1 : eol;
|
|
|
|
}
|
|
|
|
if (!*todo_list)
|
|
|
|
return error(_("No commits parsed."));
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void read_populate_todo(struct commit_list **todo_list,
|
|
|
|
struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
struct strbuf buf = STRBUF_INIT;
|
|
|
|
int fd, res;
|
|
|
|
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
fd = open(git_path_todo_file(), O_RDONLY);
|
2012-01-11 19:15:57 +01:00
|
|
|
if (fd < 0)
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
die_errno(_("Could not open %s"), git_path_todo_file());
|
2012-01-11 19:15:57 +01:00
|
|
|
if (strbuf_read(&buf, fd, 0) < 0) {
|
|
|
|
close(fd);
|
|
|
|
strbuf_release(&buf);
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
die(_("Could not read %s."), git_path_todo_file());
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
close(fd);
|
|
|
|
|
|
|
|
res = parse_insn_buffer(buf.buf, todo_list, opts);
|
|
|
|
strbuf_release(&buf);
|
|
|
|
if (res)
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
die(_("Unusable instruction sheet: %s"), git_path_todo_file());
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
static int populate_opts_cb(const char *key, const char *value, void *data)
|
|
|
|
{
|
|
|
|
struct replay_opts *opts = data;
|
|
|
|
int error_flag = 1;
|
|
|
|
|
|
|
|
if (!value)
|
|
|
|
error_flag = 0;
|
|
|
|
else if (!strcmp(key, "options.no-commit"))
|
|
|
|
opts->no_commit = git_config_bool_or_int(key, value, &error_flag);
|
|
|
|
else if (!strcmp(key, "options.edit"))
|
|
|
|
opts->edit = git_config_bool_or_int(key, value, &error_flag);
|
|
|
|
else if (!strcmp(key, "options.signoff"))
|
|
|
|
opts->signoff = git_config_bool_or_int(key, value, &error_flag);
|
|
|
|
else if (!strcmp(key, "options.record-origin"))
|
|
|
|
opts->record_origin = git_config_bool_or_int(key, value, &error_flag);
|
|
|
|
else if (!strcmp(key, "options.allow-ff"))
|
|
|
|
opts->allow_ff = git_config_bool_or_int(key, value, &error_flag);
|
|
|
|
else if (!strcmp(key, "options.mainline"))
|
|
|
|
opts->mainline = git_config_int(key, value);
|
|
|
|
else if (!strcmp(key, "options.strategy"))
|
|
|
|
git_config_string(&opts->strategy, key, value);
|
2014-01-24 01:50:58 +01:00
|
|
|
else if (!strcmp(key, "options.gpg-sign"))
|
|
|
|
git_config_string(&opts->gpg_sign, key, value);
|
2012-01-11 19:15:57 +01:00
|
|
|
else if (!strcmp(key, "options.strategy-option")) {
|
|
|
|
ALLOC_GROW(opts->xopts, opts->xopts_nr + 1, opts->xopts_alloc);
|
|
|
|
opts->xopts[opts->xopts_nr++] = xstrdup(value);
|
|
|
|
} else
|
|
|
|
return error(_("Invalid key: %s"), key);
|
|
|
|
|
|
|
|
if (!error_flag)
|
|
|
|
return error(_("Invalid value for %s: %s"), key, value);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void read_populate_opts(struct replay_opts **opts_ptr)
|
|
|
|
{
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
if (!file_exists(git_path_opts_file()))
|
2012-01-11 19:15:57 +01:00
|
|
|
return;
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
if (git_config_from_file(populate_opts_cb, git_path_opts_file(), *opts_ptr) < 0)
|
|
|
|
die(_("Malformed options sheet: %s"), git_path_opts_file());
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
static void walk_revs_populate_todo(struct commit_list **todo_list,
|
|
|
|
struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
struct commit *commit;
|
|
|
|
struct commit_list **next;
|
|
|
|
|
|
|
|
prepare_revs(opts);
|
|
|
|
|
|
|
|
next = todo_list;
|
|
|
|
while ((commit = get_revision(opts->revs)))
|
|
|
|
next = commit_list_append(commit, next);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int create_seq_dir(void)
|
|
|
|
{
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
if (file_exists(git_path_seq_dir())) {
|
2012-01-11 19:15:57 +01:00
|
|
|
error(_("a cherry-pick or revert is already in progress"));
|
|
|
|
advise(_("try \"git cherry-pick (--continue | --quit | --abort)\""));
|
|
|
|
return -1;
|
|
|
|
}
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
else if (mkdir(git_path_seq_dir(), 0777) < 0)
|
|
|
|
die_errno(_("Could not create sequencer directory %s"),
|
|
|
|
git_path_seq_dir());
|
2012-01-11 19:15:57 +01:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void save_head(const char *head)
|
|
|
|
{
|
|
|
|
static struct lock_file head_lock;
|
|
|
|
struct strbuf buf = STRBUF_INIT;
|
|
|
|
int fd;
|
|
|
|
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
fd = hold_lock_file_for_update(&head_lock, git_path_head_file(), LOCK_DIE_ON_ERROR);
|
2012-01-11 19:15:57 +01:00
|
|
|
strbuf_addf(&buf, "%s\n", head);
|
|
|
|
if (write_in_full(fd, buf.buf, buf.len) < 0)
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
die_errno(_("Could not write to %s"), git_path_head_file());
|
2012-01-11 19:15:57 +01:00
|
|
|
if (commit_lock_file(&head_lock) < 0)
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
die(_("Error wrapping up %s."), git_path_head_file());
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
static int reset_for_rollback(const unsigned char *sha1)
|
|
|
|
{
|
|
|
|
const char *argv[4]; /* reset --merge <arg> + NULL */
|
|
|
|
argv[0] = "reset";
|
|
|
|
argv[1] = "--merge";
|
|
|
|
argv[2] = sha1_to_hex(sha1);
|
|
|
|
argv[3] = NULL;
|
|
|
|
return run_command_v_opt(argv, RUN_GIT_CMD);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int rollback_single_pick(void)
|
|
|
|
{
|
|
|
|
unsigned char head_sha1[20];
|
|
|
|
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
if (!file_exists(git_path_cherry_pick_head()) &&
|
|
|
|
!file_exists(git_path_revert_head()))
|
2012-01-11 19:15:57 +01:00
|
|
|
return error(_("no cherry-pick or revert in progress"));
|
2014-07-15 21:59:36 +02:00
|
|
|
if (read_ref_full("HEAD", 0, head_sha1, NULL))
|
2012-01-11 19:15:57 +01:00
|
|
|
return error(_("cannot resolve HEAD"));
|
|
|
|
if (is_null_sha1(head_sha1))
|
|
|
|
return error(_("cannot abort from a branch yet to be born"));
|
|
|
|
return reset_for_rollback(head_sha1);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int sequencer_rollback(struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
FILE *f;
|
|
|
|
unsigned char sha1[20];
|
|
|
|
struct strbuf buf = STRBUF_INIT;
|
|
|
|
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
f = fopen(git_path_head_file(), "r");
|
2012-01-11 19:15:57 +01:00
|
|
|
if (!f && errno == ENOENT) {
|
|
|
|
/*
|
|
|
|
* There is no multiple-cherry-pick in progress.
|
|
|
|
* If CHERRY_PICK_HEAD or REVERT_HEAD indicates
|
|
|
|
* a single-cherry-pick in progress, abort that.
|
|
|
|
*/
|
|
|
|
return rollback_single_pick();
|
|
|
|
}
|
|
|
|
if (!f)
|
2016-05-08 11:47:54 +02:00
|
|
|
return error_errno(_("cannot open %s"), git_path_head_file());
|
2016-01-14 00:31:17 +01:00
|
|
|
if (strbuf_getline_lf(&buf, f)) {
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
error(_("cannot read %s: %s"), git_path_head_file(),
|
|
|
|
ferror(f) ? strerror(errno) : _("unexpected end of file"));
|
2012-01-11 19:15:57 +01:00
|
|
|
fclose(f);
|
|
|
|
goto fail;
|
|
|
|
}
|
|
|
|
fclose(f);
|
|
|
|
if (get_sha1_hex(buf.buf, sha1) || buf.buf[40] != '\0') {
|
|
|
|
error(_("stored pre-cherry-pick HEAD file '%s' is corrupt"),
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
git_path_head_file());
|
2012-01-11 19:15:57 +01:00
|
|
|
goto fail;
|
|
|
|
}
|
2016-06-06 15:23:54 +02:00
|
|
|
if (is_null_sha1(sha1)) {
|
|
|
|
error(_("cannot abort from a branch yet to be born"));
|
|
|
|
goto fail;
|
|
|
|
}
|
2012-01-11 19:15:57 +01:00
|
|
|
if (reset_for_rollback(sha1))
|
|
|
|
goto fail;
|
|
|
|
remove_sequencer_state();
|
|
|
|
strbuf_release(&buf);
|
|
|
|
return 0;
|
|
|
|
fail:
|
|
|
|
strbuf_release(&buf);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void save_todo(struct commit_list *todo_list, struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
static struct lock_file todo_lock;
|
|
|
|
struct strbuf buf = STRBUF_INIT;
|
|
|
|
int fd;
|
|
|
|
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
fd = hold_lock_file_for_update(&todo_lock, git_path_todo_file(), LOCK_DIE_ON_ERROR);
|
2012-01-11 19:15:57 +01:00
|
|
|
if (format_todo(&buf, todo_list, opts) < 0)
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
die(_("Could not format %s."), git_path_todo_file());
|
2012-01-11 19:15:57 +01:00
|
|
|
if (write_in_full(fd, buf.buf, buf.len) < 0) {
|
|
|
|
strbuf_release(&buf);
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
die_errno(_("Could not write to %s"), git_path_todo_file());
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
if (commit_lock_file(&todo_lock) < 0) {
|
|
|
|
strbuf_release(&buf);
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
die(_("Error wrapping up %s."), git_path_todo_file());
|
2012-01-11 19:15:57 +01:00
|
|
|
}
|
|
|
|
strbuf_release(&buf);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void save_opts(struct replay_opts *opts)
|
|
|
|
{
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
const char *opts_file = git_path_opts_file();
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
if (opts->no_commit)
|
|
|
|
git_config_set_in_file(opts_file, "options.no-commit", "true");
|
|
|
|
if (opts->edit)
|
|
|
|
git_config_set_in_file(opts_file, "options.edit", "true");
|
|
|
|
if (opts->signoff)
|
|
|
|
git_config_set_in_file(opts_file, "options.signoff", "true");
|
|
|
|
if (opts->record_origin)
|
|
|
|
git_config_set_in_file(opts_file, "options.record-origin", "true");
|
|
|
|
if (opts->allow_ff)
|
|
|
|
git_config_set_in_file(opts_file, "options.allow-ff", "true");
|
|
|
|
if (opts->mainline) {
|
|
|
|
struct strbuf buf = STRBUF_INIT;
|
|
|
|
strbuf_addf(&buf, "%d", opts->mainline);
|
|
|
|
git_config_set_in_file(opts_file, "options.mainline", buf.buf);
|
|
|
|
strbuf_release(&buf);
|
|
|
|
}
|
|
|
|
if (opts->strategy)
|
|
|
|
git_config_set_in_file(opts_file, "options.strategy", opts->strategy);
|
2014-01-24 01:50:58 +01:00
|
|
|
if (opts->gpg_sign)
|
|
|
|
git_config_set_in_file(opts_file, "options.gpg-sign", opts->gpg_sign);
|
2012-01-11 19:15:57 +01:00
|
|
|
if (opts->xopts) {
|
|
|
|
int i;
|
|
|
|
for (i = 0; i < opts->xopts_nr; i++)
|
|
|
|
git_config_set_multivar_in_file(opts_file,
|
|
|
|
"options.strategy-option",
|
|
|
|
opts->xopts[i], "^$", 0);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static int pick_commits(struct commit_list *todo_list, struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
struct commit_list *cur;
|
|
|
|
int res;
|
|
|
|
|
|
|
|
setenv(GIT_REFLOG_ACTION, action_name(opts), 0);
|
|
|
|
if (opts->allow_ff)
|
|
|
|
assert(!(opts->signoff || opts->no_commit ||
|
|
|
|
opts->record_origin || opts->edit));
|
|
|
|
read_and_refresh_cache(opts);
|
|
|
|
|
|
|
|
for (cur = todo_list; cur; cur = cur->next) {
|
|
|
|
save_todo(cur, opts);
|
|
|
|
res = do_pick_commit(cur->item, opts);
|
|
|
|
if (res)
|
|
|
|
return res;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Sequence of picks finished successfully; cleanup by
|
|
|
|
* removing the .git/sequencer directory
|
|
|
|
*/
|
|
|
|
remove_sequencer_state();
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int continue_single_pick(void)
|
|
|
|
{
|
|
|
|
const char *argv[] = { "commit", NULL };
|
|
|
|
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
if (!file_exists(git_path_cherry_pick_head()) &&
|
|
|
|
!file_exists(git_path_revert_head()))
|
2012-01-11 19:15:57 +01:00
|
|
|
return error(_("no cherry-pick or revert in progress"));
|
|
|
|
return run_command_v_opt(argv, RUN_GIT_CMD);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int sequencer_continue(struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
struct commit_list *todo_list = NULL;
|
|
|
|
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
if (!file_exists(git_path_todo_file()))
|
2012-01-11 19:15:57 +01:00
|
|
|
return continue_single_pick();
|
|
|
|
read_populate_opts(&opts);
|
|
|
|
read_populate_todo(&todo_list, opts);
|
|
|
|
|
|
|
|
/* Verify that the conflict has been resolved */
|
memoize common git-path "constant" files
One of the most common uses of git_path() is to pass a
constant, like git_path("MERGE_MSG"). This has two
drawbacks:
1. The return value is a static buffer, and the lifetime
is dependent on other calls to git_path, etc.
2. There's no compile-time checking of the pathname. This
is OK for a one-off (after all, we have to spell it
correctly at least once), but many of these constant
strings appear throughout the code.
This patch introduces a series of functions to "memoize"
these strings, which are essentially globals for the
lifetime of the program. We compute the value once, take
ownership of the buffer, and return the cached value for
subsequent calls. cache.h provides a helper macro for
defining these functions as one-liners, and defines a few
common ones for global use.
Using a macro is a little bit gross, but it does nicely
document the purpose of the functions. If we need to touch
them all later (e.g., because we learned how to change the
git_dir variable at runtime, and need to invalidate all of
the stored values), it will be much easier to have the
complete list.
Note that the shared-global functions have separate, manual
declarations. We could do something clever with the macros
(e.g., expand it to a declaration in some places, and a
declaration _and_ a definition in path.c). But there aren't
that many, and it's probably better to stay away from
too-magical macros.
Likewise, if we abandon the C preprocessor in favor of
generating these with a script, we could get much fancier.
E.g., normalizing "FOO/BAR-BAZ" into "git_path_foo_bar_baz".
But the small amount of saved typing is probably not worth
the resulting confusion to readers who want to grep for the
function's definition.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 11:38:57 +02:00
|
|
|
if (file_exists(git_path_cherry_pick_head()) ||
|
|
|
|
file_exists(git_path_revert_head())) {
|
2012-01-11 19:15:57 +01:00
|
|
|
int ret = continue_single_pick();
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
if (index_differs_from("HEAD", 0))
|
|
|
|
return error_dirty_index(opts);
|
|
|
|
todo_list = todo_list->next;
|
|
|
|
return pick_commits(todo_list, opts);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int single_pick(struct commit *cmit, struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
setenv(GIT_REFLOG_ACTION, action_name(opts), 0);
|
|
|
|
return do_pick_commit(cmit, opts);
|
|
|
|
}
|
|
|
|
|
|
|
|
int sequencer_pick_revisions(struct replay_opts *opts)
|
|
|
|
{
|
|
|
|
struct commit_list *todo_list = NULL;
|
|
|
|
unsigned char sha1[20];
|
2013-04-11 15:06:52 +02:00
|
|
|
int i;
|
2012-01-11 19:15:57 +01:00
|
|
|
|
|
|
|
if (opts->subcommand == REPLAY_NONE)
|
|
|
|
assert(opts->revs);
|
|
|
|
|
|
|
|
read_and_refresh_cache(opts);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Decide what to do depending on the arguments; a fresh
|
|
|
|
* cherry-pick should be handled differently from an existing
|
|
|
|
* one that is being continued
|
|
|
|
*/
|
|
|
|
if (opts->subcommand == REPLAY_REMOVE_STATE) {
|
|
|
|
remove_sequencer_state();
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
if (opts->subcommand == REPLAY_ROLLBACK)
|
|
|
|
return sequencer_rollback(opts);
|
|
|
|
if (opts->subcommand == REPLAY_CONTINUE)
|
|
|
|
return sequencer_continue(opts);
|
|
|
|
|
2013-04-11 15:06:52 +02:00
|
|
|
for (i = 0; i < opts->revs->pending.nr; i++) {
|
|
|
|
unsigned char sha1[20];
|
|
|
|
const char *name = opts->revs->pending.objects[i].name;
|
|
|
|
|
|
|
|
/* This happens when using --stdin. */
|
|
|
|
if (!strlen(name))
|
|
|
|
continue;
|
|
|
|
|
|
|
|
if (!get_sha1(name, sha1)) {
|
2013-05-09 22:27:49 +02:00
|
|
|
if (!lookup_commit_reference_gently(sha1, 1)) {
|
|
|
|
enum object_type type = sha1_object_info(sha1, NULL);
|
2013-04-11 15:06:52 +02:00
|
|
|
die(_("%s: can't cherry-pick a %s"), name, typename(type));
|
2013-05-09 22:27:49 +02:00
|
|
|
}
|
2013-04-11 15:06:52 +02:00
|
|
|
} else
|
|
|
|
die(_("%s: bad revision"), name);
|
|
|
|
}
|
|
|
|
|
2012-01-11 19:15:57 +01:00
|
|
|
/*
|
|
|
|
* If we were called as "git cherry-pick <commit>", just
|
|
|
|
* cherry-pick/revert it, set CHERRY_PICK_HEAD /
|
|
|
|
* REVERT_HEAD, and don't touch the sequencer state.
|
|
|
|
* This means it is possible to cherry-pick in the middle
|
|
|
|
* of a cherry-pick sequence.
|
|
|
|
*/
|
|
|
|
if (opts->revs->cmdline.nr == 1 &&
|
|
|
|
opts->revs->cmdline.rev->whence == REV_CMD_REV &&
|
|
|
|
opts->revs->no_walk &&
|
|
|
|
!opts->revs->cmdline.rev->flags) {
|
|
|
|
struct commit *cmit;
|
|
|
|
if (prepare_revision_walk(opts->revs))
|
|
|
|
die(_("revision walk setup failed"));
|
|
|
|
cmit = get_revision(opts->revs);
|
|
|
|
if (!cmit || get_revision(opts->revs))
|
|
|
|
die("BUG: expected exactly one commit from walk");
|
|
|
|
return single_pick(cmit, opts);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Start a new cherry-pick/ revert sequence; but
|
|
|
|
* first, make sure that an existing one isn't in
|
|
|
|
* progress
|
|
|
|
*/
|
|
|
|
|
|
|
|
walk_revs_populate_todo(&todo_list, opts);
|
|
|
|
if (create_seq_dir() < 0)
|
|
|
|
return -1;
|
2016-06-06 15:23:54 +02:00
|
|
|
if (get_sha1("HEAD", sha1) && (opts->action == REPLAY_REVERT))
|
|
|
|
return error(_("Can't revert as initial commit"));
|
2012-01-11 19:15:57 +01:00
|
|
|
save_head(sha1_to_hex(sha1));
|
|
|
|
save_opts(opts);
|
|
|
|
return pick_commits(todo_list, opts);
|
|
|
|
}
|
2012-09-14 08:52:03 +02:00
|
|
|
|
2013-02-12 11:17:35 +01:00
|
|
|
void append_signoff(struct strbuf *msgbuf, int ignore_footer, unsigned flag)
|
2012-09-14 08:52:03 +02:00
|
|
|
{
|
2013-02-12 11:17:35 +01:00
|
|
|
unsigned no_dup_sob = flag & APPEND_SIGNOFF_DEDUP;
|
2012-09-14 08:52:03 +02:00
|
|
|
struct strbuf sob = STRBUF_INIT;
|
2013-02-12 11:17:35 +01:00
|
|
|
int has_footer;
|
2012-09-14 08:52:03 +02:00
|
|
|
|
|
|
|
strbuf_addstr(&sob, sign_off_header);
|
|
|
|
strbuf_addstr(&sob, fmt_name(getenv("GIT_COMMITTER_NAME"),
|
|
|
|
getenv("GIT_COMMITTER_EMAIL")));
|
|
|
|
strbuf_addch(&sob, '\n');
|
2013-02-12 11:17:35 +01:00
|
|
|
|
|
|
|
/*
|
|
|
|
* If the whole message buffer is equal to the sob, pretend that we
|
|
|
|
* found a conforming footer with a matching sob
|
|
|
|
*/
|
|
|
|
if (msgbuf->len - ignore_footer == sob.len &&
|
|
|
|
!strncmp(msgbuf->buf, sob.buf, sob.len))
|
|
|
|
has_footer = 3;
|
|
|
|
else
|
|
|
|
has_footer = has_conforming_footer(msgbuf, &sob, ignore_footer);
|
|
|
|
|
2013-02-12 11:33:42 +01:00
|
|
|
if (!has_footer) {
|
|
|
|
const char *append_newlines = NULL;
|
|
|
|
size_t len = msgbuf->len - ignore_footer;
|
|
|
|
|
2013-02-22 23:05:27 +01:00
|
|
|
if (!len) {
|
|
|
|
/*
|
|
|
|
* The buffer is completely empty. Leave foom for
|
|
|
|
* the title and body to be filled in by the user.
|
|
|
|
*/
|
2013-02-12 11:33:42 +01:00
|
|
|
append_newlines = "\n\n";
|
2013-02-22 23:05:27 +01:00
|
|
|
} else if (msgbuf->buf[len - 1] != '\n') {
|
|
|
|
/*
|
|
|
|
* Incomplete line. Complete the line and add a
|
|
|
|
* blank one so that there is an empty line between
|
|
|
|
* the message body and the sob.
|
|
|
|
*/
|
|
|
|
append_newlines = "\n\n";
|
|
|
|
} else if (len == 1) {
|
|
|
|
/*
|
|
|
|
* Buffer contains a single newline. Add another
|
|
|
|
* so that we leave room for the title and body.
|
|
|
|
*/
|
|
|
|
append_newlines = "\n";
|
|
|
|
} else if (msgbuf->buf[len - 2] != '\n') {
|
|
|
|
/*
|
|
|
|
* Buffer ends with a single newline. Add another
|
|
|
|
* so that there is an empty line between the message
|
|
|
|
* body and the sob.
|
|
|
|
*/
|
2013-02-12 11:33:42 +01:00
|
|
|
append_newlines = "\n";
|
2013-02-22 23:05:27 +01:00
|
|
|
} /* else, the buffer already ends with two newlines. */
|
2013-02-12 11:33:42 +01:00
|
|
|
|
|
|
|
if (append_newlines)
|
|
|
|
strbuf_splice(msgbuf, msgbuf->len - ignore_footer, 0,
|
|
|
|
append_newlines, strlen(append_newlines));
|
2012-09-14 08:52:03 +02:00
|
|
|
}
|
2013-02-12 11:17:35 +01:00
|
|
|
|
|
|
|
if (has_footer != 3 && (!no_dup_sob || has_footer != 2))
|
|
|
|
strbuf_splice(msgbuf, msgbuf->len - ignore_footer, 0,
|
|
|
|
sob.buf, sob.len);
|
|
|
|
|
2012-09-14 08:52:03 +02:00
|
|
|
strbuf_release(&sob);
|
|
|
|
}
|