From: Avery Pennarun <apenwarr@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Bradley Wagner <bradley.wagner@hannonhill.com>, git@vger.kernel.org
Subject: Re: Possible feature request for merge and pull
Date: Wed, 28 Jul 2010 16:49:11 -0400 [thread overview]
Message-ID: <AANLkTikA2jWu76aPUNG+B7Nwc9eDzoU93VcGvUFWR0Ri@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinRvq71GS5WVdWs9zP5QSJ=TjCWBgTfRGn2Qub0@mail.gmail.com>
On Wed, Jul 28, 2010 at 3:34 AM, Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> On Wed, Jul 28, 2010 at 01:24, Bradley Wagner
> <bradley.wagner@hannonhill.com> wrote:
>> I would love to be able to use the -m flag and --log together with git
>> merge and pull to be able to create a custom commit message but also
>> include one-line summaries of each of the commits being merged/pulled.
>
> This sort of thing has vaguely come up before, and it was mentioned
> that you can just use a small script that calls git-filter-branch or
> git-rebase -i.
>
> It's easy to rewrite the commits you just pulled, having some feature
> that e.g. adds a custom message to the beginning of each of them would
> just impose an artificial limitation and overlap with existing (and
> more powerful) functionality.
If I understand correctly, the request is not to rewrite the pulled
commits, but just to produce a nice message in the newly-created merge
commit.
It sounds like --log and -m are currently incompatible, in that -m
overrides --log, and that's not the desired behaviour. Bradley: this
is probably a relatively easy fix to make, in case you're looking to
get into some git hacking. :)
Have fun,
Avery
next prev parent reply other threads:[~2010-07-28 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 1:24 Possible feature request for merge and pull Bradley Wagner
2010-07-28 7:34 ` Ævar Arnfjörð Bjarmason
2010-07-28 20:49 ` Avery Pennarun [this message]
2010-07-28 20:55 ` Bradley Wagner
2010-07-29 1:03 ` Jeff King
2010-07-29 1:21 ` Bradley Wagner
2010-07-29 1:27 ` Jonathan Nieder
2010-07-29 1:30 ` Bradley Wagner
2010-07-29 4:20 ` Bradley Wagner
2010-07-29 4:22 ` Avery Pennarun
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=AANLkTikA2jWu76aPUNG+B7Nwc9eDzoU93VcGvUFWR0Ri@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=avarab@gmail.com \
--cc=bradley.wagner@hannonhill.com \
--cc=git@vger.kernel.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).