From: Jeff King <peff@peff.net>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Bradley Wagner" <bradley.wagner@hannonhill.com>,
git@vger.kernel.org
Subject: Re: Possible feature request for merge and pull
Date: Wed, 28 Jul 2010 21:03:41 -0400 [thread overview]
Message-ID: <20100729010341.GA25732@coredump.intra.peff.net> (raw)
In-Reply-To: <AANLkTikA2jWu76aPUNG+B7Nwc9eDzoU93VcGvUFWR0Ri@mail.gmail.com>
On Wed, Jul 28, 2010 at 04:49:11PM -0400, Avery Pennarun wrote:
> 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. :)
Really? I get:
$ mkdir repo && cd repo && git init &&
echo content >file && git add file && git commit -m one &&
echo content >>file && git commit -a -m two &&
git checkout -b other HEAD^ &&
echo content >file2 && git add file2 && git commit -m three &&
git merge --log -m "custom message" master &&
git show
commit fa21035ea5f5437e8664a5d249e7ab88ee3f0e75
Merge: d12be4a 4dc5cba
Author: Jeff King <peff@peff.net>
Date: Wed Jul 28 20:50:39 2010 -0400
custom message
* master:
two
which seems to be what was asked for. So is the problem just that
git-pull does not take "-m"?
-Peff
next prev parent reply other threads:[~2010-07-29 1:03 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
2010-07-28 20:55 ` Bradley Wagner
2010-07-29 1:03 ` Jeff King [this message]
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=20100729010341.GA25732@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=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).