summaryrefslogtreecommitdiff
path: root/server-info.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2014-10-28 20:04:38 (GMT)
committerJunio C Hamano <gitster@pobox.com>2014-10-28 21:04:28 (GMT)
commit261f315bebfa9af2d09f20211960100ff06f87cb (patch)
tree398928f70a310b7e06d33025a5126e6403fad74a /server-info.c
parent073bd75e177aa9f1fc42b152a38e251c7156dfe0 (diff)
downloadgit-261f315bebfa9af2d09f20211960100ff06f87cb.zip
git-261f315bebfa9af2d09f20211960100ff06f87cb.tar.gz
git-261f315bebfa9af2d09f20211960100ff06f87cb.tar.bz2
merge & sequencer: turn "Conflicts:" hint into a comment
Just like other hints such as "Changes to be committed" we show in the editor to remind the committer what paths were involved in the resulting commit to help improving their log message, this section is merely a reminder. Traditionally, it was not made into comments primarily because it has to be generated outside the wt-status infrastructure, and also because it was meant as a bit stronger reminder than the others (i.e. explaining how you resolved conflicts is much more important than mentioning what you did to every paths involved in the commit). But that still does not make this hint a part of the log message proper, and not showing it as a comment is inviting mistakes. Note that we still notice "Conflicts:" followed by list of indented pathnames as an old-style cruft and insert a new Signed-off-by: before it. This is so that "commit --amend -s" adds the new S-o-b at the right place when used on an older commit. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'server-info.c')
0 files changed, 0 insertions, 0 deletions