From: Stephen Bash <bash@genarts.com>
To: in-gitvger@baka.org
Cc: "Todd A. Jacobs" <nospam+listmail@codegnome.org>, git@vger.kernel.org
Subject: Re: Prompt for merge message?
Date: Thu, 6 Oct 2011 16:15:38 -0400 (EDT) [thread overview]
Message-ID: <21983420.46542.1317932138649.JavaMail.root@mail.hq.genarts.com> (raw)
In-Reply-To: <201110061851.p96Ipfui016139@no.baka.org>
----- Original Message -----
> From: in-gitvger@baka.org
> Sent: Thursday, October 6, 2011 2:51:41 PM
> Subject: Re: Prompt for merge message?
>
> In message <20111006182534.GA13628@vfa-6h>, Jacob Helwig writes:
>
> On Thu, 06 Oct 2011 10:49:02 -0700, Todd A. Jacobs wrote:
>
> > I often find myself using "--no-ff -m foo" for merging short-lived
> > branches, because the merge commit usually needs to say something
> > about having finished a feature rather than referring to a branch
> > that
> > will be deleted shortly anyway. However, it's a little annoying to
> > have to always write the commit message on the command-line,
> > especially in cases where a more expository multi-line message would
> > be useful.
>
> "git merge --no-ff --no-commit branch_foo && git commit" ?
>
> While not ideal, you can use a multi-line message on the command line.
> I do it all of the time. Popping up an editor like in the separated
> workflow is more user friendly.
>
> ----------------------------------------------------------------------
> git merge --no-ff -m "My feature is very complex
>
> It requires multiple lines to explain.
>
> Or perhaps I am too verbose." branch_foo
> ----------------------------------------------------------------------
And not so helpful if you want to use the --log option to pre-populate the merge message (which I often run into).
Thanks,
Stephen
next prev parent reply other threads:[~2011-10-06 20:15 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 [this message]
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
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=21983420.46542.1317932138649.JavaMail.root@mail.hq.genarts.com \
--to=bash@genarts.com \
--cc=git@vger.kernel.org \
--cc=in-gitvger@baka.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).