21531927e4
This reverts commit 489947cee5, which
stopped treating merges into the 'master' branch as special when
preparing the default merge message. As the goal was not to have
any single branch designated as special, it solved it by leaving the
"into <branchname>" at the end of the title of the default merge
message for any and all branches. An obvious and easy alternative
to treat everybody equally could have been to remove it for every
branch, but that involves loss of information.
We'll introduce a new mechanism to let end-users specify merges into
which branches would omit the "into <branchname>" from the title of
the default merge message, and make the mechanism, when unconfigured,
treat the traditional 'master' special again, so all the changes to
the tests we made earlier will become unnecessary, as these tests
will be run without configuring the said new mechanism.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
37 lines
456 B
Plaintext
37 lines
456 B
Plaintext
$ git show master
|
|
commit 59d314ad6f356dd08601a4cd5e530381da3e3c64
|
|
Merge: 9a6d494 c7a2ab9
|
|
Author: A U Thor <author@example.com>
|
|
Date: Mon Jun 26 00:04:00 2006 +0000
|
|
|
|
Merge branch 'side'
|
|
|
|
diff --cc dir/sub
|
|
index cead32e,7289e35..992913c
|
|
--- a/dir/sub
|
|
+++ b/dir/sub
|
|
@@@ -1,6 -1,4 +1,8 @@@
|
|
A
|
|
B
|
|
+C
|
|
+D
|
|
+E
|
|
+F
|
|
+ 1
|
|
+ 2
|
|
diff --cc file0
|
|
index b414108,f4615da..10a8a9f
|
|
--- a/file0
|
|
+++ b/file0
|
|
@@@ -1,6 -1,6 +1,9 @@@
|
|
1
|
|
2
|
|
3
|
|
+4
|
|
+5
|
|
+6
|
|
+ A
|
|
+ B
|
|
+ C
|
|
$
|