From: Johannes Sixt <j.sixt@viscovery.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Let format-patch and rebase ignore trivial merges.
Date: Fri, 18 Dec 2009 14:22:27 +0100 [thread overview]
Message-ID: <4B2B8213.1090104@viscovery.net> (raw)
In-Reply-To: <20091218130603.GA6193@pcpool00.mathematik.uni-freiburg.de>
Please do not cull Cc list.
Bernhard R. Link schrieb:
> format-patch has to choose a parent. Choosing the first one make the
> most sense for me (as the first is the only real 'special' one).
> In the workflows I envision the first parent would also be the one with
> the clean history.
Then use
git format-patch --first-parent upstream..
-- Hannes
next prev parent reply other threads:[~2009-12-18 13:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 16:45 [PATCH] Let format-patch and rebase ignore trivial merges Bernhard R. Link
2009-12-16 16:53 ` Johannes Sixt
2009-12-17 9:35 ` Bernhard R. Link
2009-12-17 11:40 ` Johannes Sixt
2009-12-17 21:48 ` Bernhard R. Link
2009-12-17 22:44 ` Junio C Hamano
2009-12-18 13:06 ` Bernhard R. Link
2009-12-18 13:22 ` Johannes Sixt [this message]
2009-12-18 14:47 ` Bernhard R. Link
2009-12-18 15:11 ` [PATCH v2] " Bernhard R. Link
2009-12-18 18:23 ` 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=4B2B8213.1090104@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).