From: Junio C Hamano <gitster@pobox.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Nathan Yergler <nathan@creativecommons.org>,
Michael J Gruber <git@drmicha.warpmail.net>,
Asheesh Laroia <asheesh@asheesh.org>,
git@vger.kernel.org
Subject: [PATCH 3/3] git commit: pathspec without -i/-o implies -i semantics during a merge
Date: Thu, 22 Jan 2009 22:21:49 -0800 [thread overview]
Message-ID: <7vy6x235ky.fsf_-_@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7viqo64kfo.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Thu, 22 Jan 2009 22:15:39 -0800")
"git commit paths..." has been a short-hand for "git commit -o paths..."
since v1.3.0 and let you create a commit skipping any other updated state
staged in the index. The "--only" semantics (aka "partial commit") is
always wrong during a conflicted merge resolution, and we rejected both
"git commit paths..." and "git commit -o paths..." forms during a merge.
On the other hand, "git commit -i paths..." (aka "an also commit", which
asks to commit what you staged in the index, and also the paths you may or
may not have git-add'ed) is accepted, as it is a way to register the
contents you fixed up to the index and commit the result.
This makes "git commit paths..." form default to "git commit -i paths"
semantics only during a merge, restoring the pre-v1.3.0 behaviour. The
codepath to create a non-merge commit is not affected and still defaults
to the "--only" semantics.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
builtin-commit.c | 14 ++++++++++++--
t/t7501-commit.sh | 2 +-
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/builtin-commit.c b/builtin-commit.c
index d861263..4cb1985 100644
--- a/builtin-commit.c
+++ b/builtin-commit.c
@@ -74,6 +74,7 @@ static struct strbuf message;
enum {
MSG_AMEND_CLEVER,
MSG_ASSUME_PARTIAL,
+ MSG_ASSUME_ALSO_DURING_MERGE
};
static void set_partial_commit_message(int msgnum)
@@ -87,6 +88,9 @@ static void set_partial_commit_message(int msgnum)
case MSG_ASSUME_PARTIAL:
msg = "Explicit paths specified without -i nor -o; assuming --only paths...";
break;
+ case MSG_ASSUME_ALSO_DURING_MERGE:
+ msg = "Paths specified without -i nor -o during a merge; assuming -i";
+ break;
default:
die("Oops (%d) is not a valid message number", msgnum);
break;
@@ -812,8 +816,14 @@ static int parse_and_validate_options(int argc, const char *argv[],
die("No paths with --include/--only does not make sense.");
if (argc == 0 && only && amend)
set_partial_commit_message(MSG_AMEND_CLEVER);
- if (argc > 0 && !also && !only)
- set_partial_commit_message(MSG_ASSUME_PARTIAL);
+ if (argc > 0 && !also && !only) {
+ if (!in_merge)
+ set_partial_commit_message(MSG_ASSUME_PARTIAL);
+ else {
+ set_partial_commit_message(MSG_ASSUME_ALSO_DURING_MERGE);
+ also = 1;
+ }
+ }
if (!cleanup_arg || !strcmp(cleanup_arg, "default"))
cleanup_mode = use_editor ? CLEANUP_ALL : CLEANUP_SPACE;
else if (!strcmp(cleanup_arg, "verbatim"))
diff --git a/t/t7501-commit.sh b/t/t7501-commit.sh
index 0c10105..68892de 100755
--- a/t/t7501-commit.sh
+++ b/t/t7501-commit.sh
@@ -399,7 +399,7 @@ test_expect_success 'allow --include during a merge' '
git reset --hard
'
-test_expect_failure 'assume --include during a merge' '
+test_expect_success 'assume --include during a merge' '
git checkout HEAD^0 &&
git reset --hard the-other-side-says-nitfol &&
test_must_fail git merge one-side-says-frotz &&
--
1.6.1.265.g9a013
next prev parent reply other threads:[~2009-01-23 6:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 21:00 Short "git commit $file" syntax fails in the face of a resolved conflict Asheesh Laroia
2009-01-21 21:35 ` Michael J Gruber
2009-01-21 21:46 ` Nathan Yergler
2009-01-22 7:28 ` Johannes Sixt
2009-01-22 9:17 ` Michael J Gruber
2009-01-23 0:45 ` Nanako Shiraishi
2009-01-23 2:55 ` Asheesh Laroia
2009-01-23 6:15 ` Junio C Hamano
2009-01-23 6:17 ` [PATCH 1/3] Add "partial commit" tests during a conflicted merge Junio C Hamano
2009-01-23 7:09 ` Johannes Sixt
2009-01-23 7:16 ` Junio C Hamano
2009-01-23 7:32 ` Johannes Sixt
2009-01-23 7:39 ` Junio C Hamano
2009-01-23 6:19 ` [PATCH 2/3] builtin-commit: shorten eye-sore overlong lines Junio C Hamano
2009-01-23 6:21 ` Junio C Hamano [this message]
2009-01-23 9:51 ` [PATCH 3/3] git commit: pathspec without -i/-o implies -i semantics during a merge Pieter de Bie
2009-01-23 17:01 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vy6x235ky.fsf_-_@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=asheesh@asheesh.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=nanako3@lavabit.com \
--cc=nathan@creativecommons.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).