From: Junio C Hamano <gitster@pobox.com>
To: "Todd A. Jacobs" <nospam+listmail@codegnome.org>
Cc: git@vger.kernel.org
Subject: Re: Prompt for merge message?
Date: Thu, 06 Oct 2011 20:07:31 -0700 [thread overview]
Message-ID: <7vy5wxwlcc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <403e37d1-bdd3-46fc-9a9a-e8aab3a2d3ba@f6g2000vbm.googlegroups.com> (Todd A. Jacobs's message of "Thu, 6 Oct 2011 18:15:11 -0700 (PDT)")
"Todd A. Jacobs" <nospam+listmail@codegnome.org> writes:
> On Oct 6, 6:02 pm, Junio C Hamano <gits...@pobox.com> wrote:
>> Others commented on the current practices and gave their own useful tips
>> already, but an additional hint is to name your branch more sensibly, so
>> that you do not feel it is useless to record it in the history.
> ...
> Ultimately, I guess what I'm really agitating for is just an editor
> option for merge commits. If you take work-flow out of the equation,
> isn't there still a case for easily-editable merge messages?
I do not see any reason for you to be agitated. All you need to do is to
read beyond what you chose to quote from my message, read that part before
omitting from your quote ;-).
prev parent reply other threads:[~2011-10-07 3:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 17:49 Prompt for merge message? Todd A. Jacobs
2011-10-06 18:25 ` Jacob Helwig
2011-10-06 18:51 ` in-gitvger
2011-10-06 20:15 ` Stephen Bash
2011-10-06 20:19 ` Andreas Krey
2011-10-06 22:02 ` Junio C Hamano
2011-10-06 22:09 ` Shawn Pearce
2011-10-06 23:17 ` Junio C Hamano
2011-10-07 1:15 ` Todd A. Jacobs
2011-10-07 3:07 ` Junio C Hamano [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=7vy5wxwlcc.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nospam+listmail@codegnome.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).