summaryrefslogtreecommitdiff
path: root/gitweb/gitweb.perl
diff options
context:
space:
mode:
authorThomas Rast <trast@student.ethz.ch>2012-01-30 21:25:30 +0100
committerJunio C Hamano <gitster@pobox.com>2012-01-31 12:04:38 -0800
commitf26af3fcbcbd27392b8c94b1e4eb6e671b2466ab (patch)
treed935aef25ff4e5fee78f373108da9ad396993b86 /gitweb/gitweb.perl
parent828ea97de486c1693d6e4f2c7347acb50235a85d (diff)
downloadgit-f26af3fcbcbd27392b8c94b1e4eb6e671b2466ab.tar.gz
merge: add instructions to the commit message when editingtr/merge-edit-guidance
Before f824628 (merge: use editor by default in interactive sessions, 2012-01-10), git-merge only started an editor if the user explicitly asked for it with --edit. Thus it seemed unlikely that the user would need extra guidance. After f824628 the _normal_ thing is to start an editor. Give at least an indication of why we are doing it. The sentence about justification is one of the few things about standard git that are not agnostic to the workflow that the user chose. However, f824628 was proposed by Linus specifically to discourage users from merging unrelated upstream progress into topic branches. So we may as well take another step in the same direction. Signed-off-by: Thomas Rast <trast@student.ethz.ch> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'gitweb/gitweb.perl')
0 files changed, 0 insertions, 0 deletions