From: Alexander Litvinov <litvinov2004@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: How to enhance merge commit message ?
Date: Tue, 30 Jan 2007 11:23:59 +0600 [thread overview]
Message-ID: <200701301123.59687.litvinov2004@gmail.com> (raw)
In-Reply-To: <7v8xfl6s27.fsf@assigned-by-dhcp.cox.net>
В сообщении от Tuesday 30 January 2007 10:45 Junio C Hamano написал(a):
> $ grep -A2 '^merge\.summary' Documentation/config.txt
> merge.summary::
> Whether to include summaries of merged commits in newly created
> merge commit messages. False by default.
Thanks !
> This is a good option if you are doing the top-level "bundling
> of others' work -- people will base their further work on this"
> merges. On the other hand, if you are merging from your uplevel
> because your work depends on something that was updated recently,
> having the merge summary is often pointless (because the merge
> would bring in many mostly unrelated commits, in addition to that
> something your work depends on). I think Linus has explicitly
> asked this option not enabled by people he pulls from for this
> reason.
I understand your point.
prev parent reply other threads:[~2007-01-30 5:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 4:32 How to enhance merge commit message ? Alexander Litvinov
2007-01-30 4:45 ` Junio C Hamano
2007-01-30 5:23 ` Alexander Litvinov [this message]
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=200701301123.59687.litvinov2004@gmail.com \
--to=litvinov2004@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).