From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Stephan Beyer <s-beyer@gmx.net>, git@vger.kernel.org
Subject: Re: 'next' will be rewound shortly
Date: Fri, 27 Jun 2008 14:28:29 -0700 [thread overview]
Message-ID: <7vd4m2r2iq.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080627192819.GC2058@genesis.frugalware.org> (Miklos Vajna's message of "Fri, 27 Jun 2008 21:28:19 +0200")
Miklos Vajna <vmiklos@frugalware.org> writes:
> On Fri, Jun 27, 2008 at 07:19:48PM +0200, Stephan Beyer <s-beyer@gmx.net> wrote:
>> -m <msg>::
>> The commit message to be used for the merge commit (in case
>> it is created). The `git-fmt-merge-msg` script can be used
>> to give a good default for automated `git-merge` invocations.
>>
>> So it is not mentioned that a standard message is appended, and thus the
>> original behavior is somehow "buggy" :)
>
> Ah, OK. Then the code and the documentation differs and that's a bug,
> sure.
>
> From git-merge.sh:
>
> # All the rest are the commits being merged; prepare
> # the standard merge summary message to be appended to
> # the given message.
>
> I did builtin-merge based on git-merge.sh, not the manpage. ;-)
Following git tradition, manpage came after the command's behaviour has
been long established. It will be a behaviour change, and it is open to
debate if the new behaviour is better or if the proposed change of
behaviour hurts existing users.
next prev parent reply other threads:[~2008-06-27 21:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 23:24 [ANNOUNCE] GIT 1.5.6 Junio C Hamano
2008-06-19 7:24 ` A note from the maintainer Junio C Hamano
2008-06-19 9:17 ` 'next' will be rewound shortly Junio C Hamano
2008-06-27 16:12 ` Stephan Beyer
2008-06-27 16:34 ` Miklos Vajna
2008-06-27 17:19 ` Stephan Beyer
2008-06-27 19:28 ` Miklos Vajna
2008-06-27 21:28 ` Junio C Hamano [this message]
2008-06-27 21:36 ` Miklos Vajna
2008-06-27 23:41 ` Stephan Beyer
2008-06-28 0:05 ` Junio C Hamano
2008-07-14 5:51 ` A note from the maintainer Junio C Hamano
2008-06-22 16:54 ` [ANNOUNCE] GIT 1.5.6 Steffen Prohaska
2008-06-26 6:21 ` [ANNOUNCE] GIT 1.5.6.1 Junio C Hamano
2008-07-01 11:29 ` Steffen Prohaska
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=7vd4m2r2iq.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=s-beyer@gmx.net \
--cc=vmiklos@frugalware.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).