From: Andrey Hsiao <andreyhsiao@gmail.com>
To: git@vger.kernel.org
Subject: Git merge commit message issue
Date: Mon, 6 Jul 2015 23:45:51 +0800 [thread overview]
Message-ID: <CAArk4YMzN_dY3SOKEjtpykunMjS5bWXYazcLxXb4TGTGP_zArw@mail.gmail.com> (raw)
Dear list:
In the past, when we do the merge in git, if conflicts occurred, when
we commit, the conflict list will be appended to the default commit
message automatically.
eg:
Conflicts:
....a.java
....b.java
Today, after using Git 2.3.0 for a merge, it seems now the conflict
list was commented out by default.
I just searched a bit in the release notes, don't know whether below
item has to do with this change.
----
"git interpret-trailers" learned to properly handle the "Conflicts:"
block at the end.
----
We quite rely on the default generated conflict list to reminder us
about the "history".
Is this the default behavior now (conflict list commented out)?
Thanks
Best Regards
next reply other threads:[~2015-07-06 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 15:45 Andrey Hsiao [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-06 15:41 Git merge commit message issue Andrey Hsiao
2015-07-06 16:08 ` Matthieu Moy
2015-07-06 16:16 ` Andrey Hsiao
2015-07-06 16:33 ` Matthieu Moy
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=CAArk4YMzN_dY3SOKEjtpykunMjS5bWXYazcLxXb4TGTGP_zArw@mail.gmail.com \
--to=andreyhsiao@gmail.com \
--cc=git@vger.kernel.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).