From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] merge: deprecate 'git merge <message> HEAD <commit>' syntax
Date: Thu, 26 Mar 2015 09:20:15 -0400 [thread overview]
Message-ID: <20150326132014.GA16427@peff.net> (raw)
In-Reply-To: <xmqqvbhoz75m.fsf@gitster.dls.corp.google.com>
On Wed, Mar 25, 2015 at 09:58:45PM -0700, Junio C Hamano wrote:
> We had this in "git merge" manual for eternity:
>
> 'git merge' <msg> HEAD <commit>...
>
> [This] syntax (<msg> `HEAD` <commit>...) is supported for
> historical reasons. Do not use it from the command line or in
> new scripts. It is the same as `git merge -m <msg> <commit>...`.
It would be nice to see this ancient wart ago. I agree we need a
deprecation period, though, as you've outlined here.
> builtin/merge.c | 1 +
> git-cvsimport.perl | 2 +-
> git-pull.sh | 2 +-
> t/t3402-rebase-merge.sh | 2 +-
> t/t6021-merge-criss-cross.sh | 6 +++---
> t/t9402-git-cvsserver-refs.sh | 2 +-
> 6 files changed, 8 insertions(+), 7 deletions(-)
Maybe squash in:
diff --git a/t/t6020-merge-df.sh b/t/t6020-merge-df.sh
index 27c3d73..2af1bee 100755
--- a/t/t6020-merge-df.sh
+++ b/t/t6020-merge-df.sh
@@ -24,7 +24,7 @@ test_expect_success 'prepare repository' '
'
test_expect_success 'Merge with d/f conflicts' '
- test_expect_code 1 git merge "merge msg" B master
+ test_expect_code 1 git merge -m "merge msg" master
'
test_expect_success 'F/D conflict' '
We do not call it HEAD here, but the setup test just before has put us
on branch B, so I think it is equivalent.
-Peff
next prev parent reply other threads:[~2015-03-26 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 4:58 [PATCH] merge: deprecate 'git merge <message> HEAD <commit>' syntax Junio C Hamano
2015-03-26 5:00 ` [PATCH] merge: drop " Junio C Hamano
2015-03-26 13:20 ` Jeff King [this message]
2015-03-26 13:51 ` [PATCH] merge: deprecate " Eric Sunshine
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=20150326132014.GA16427@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.