git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Bertrand Jacquin <beber.mailing@gmail.com>
Cc: git@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: git-feed-mail-list.sh
Date: Tue, 09 May 2006 00:15:29 -0700	[thread overview]
Message-ID: <7vlktb8y9a.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0605081805290.3718@g5.osdl.org> (Linus Torvalds's message of "Mon, 8 May 2006 18:18:17 -0700 (PDT)")

Linus Torvalds <torvalds@osdl.org> writes:

> On Tue, 9 May 2006, Bertrand Jacquin wrote:
>
>> On 5/9/06, Linus Torvalds <torvalds@osdl.org> wrote:
>> > 
>> > Ie you could probably more easily parse the data from something like
>> > 
>> >         git show -B --patch-with-stat --pretty=fuller $commit
>> 
>> Is there a way to track merge like that ? Documentation is not very
>> clear and near from empty.
>
> Sure.
>
> If you want to track merges and get their patches, add the "--cc" flag, 
> which tells git to use the "conflict combination patch" that shows any 
> visible conflicts.

Actually, show defaults to --cc so what's shown is good as is.

> That said, the diffstat for merges is usually just a lot of noise. It's 
> sometimes nice (you've merged from a topic branch), but if you have merged 
> from the mainline _into_ a topic branch, it's just annoying.

True.  We made --cc --patch-with-stat to do the combined patch
text with diffstat for first-parent-diff to make it most natural
for merging into upstream, not merging from upstream.

      reply	other threads:[~2006-05-09  7:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 17:48 git-feed-mail-list.sh David Woodhouse
2006-05-04  4:35 ` git-feed-mail-list.sh Junio C Hamano
2006-05-04  5:16   ` git-feed-mail-list.sh Junio C Hamano
2006-05-08 23:44   ` git-feed-mail-list.sh David Woodhouse
2006-05-09  0:19     ` git-feed-mail-list.sh Linus Torvalds
2006-05-09  0:28       ` git-feed-mail-list.sh David Woodhouse
2006-05-09  0:36         ` git-feed-mail-list.sh Junio C Hamano
2006-05-09  0:53           ` git-feed-mail-list.sh Bertrand Jacquin
2006-05-09  0:57             ` git-feed-mail-list.sh Junio C Hamano
2006-05-09  0:59               ` git-feed-mail-list.sh Bertrand Jacquin
2006-05-09  0:45         ` git-feed-mail-list.sh Linus Torvalds
2006-05-09  1:01           ` git-feed-mail-list.sh David Woodhouse
2006-05-09  1:05             ` git-feed-mail-list.sh Junio C Hamano
2006-05-09  1:12               ` git-feed-mail-list.sh David Woodhouse
2006-05-10  8:49                 ` git-feed-mail-list.sh Martin Mares
2006-05-09  1:27             ` git-feed-mail-list.sh Linus Torvalds
2006-05-09  0:55       ` git-feed-mail-list.sh Bertrand Jacquin
2006-05-09  1:03         ` git-feed-mail-list.sh Junio C Hamano
2006-05-09  1:09           ` git-feed-mail-list.sh Bertrand Jacquin
2006-05-09  2:41             ` git-feed-mail-list.sh Junio C Hamano
2006-05-09  3:06               ` git-feed-mail-list.sh Linus Torvalds
2006-05-09  7:32                 ` git-feed-mail-list.sh Junio C Hamano
2006-05-09  1:18         ` git-feed-mail-list.sh Linus Torvalds
2006-05-09  7:15           ` 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=7vlktb8y9a.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=beber.mailing@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.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).