From: "David Kågedal" <davidk@lysator.liu.se>
To: git@vger.kernel.org
Subject: [PATCH] Document --ignore-if-in-upstream in git-format-patch
Date: Thu, 18 Jan 2007 12:27:35 +0100 [thread overview]
Message-ID: <8764b4fuc8.fsf@morpheus.local> (raw)
---
Documentation/git-format-patch.txt | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
I looked at the code, and tried to guess what it actually did. This
documentation doesn't really explain how or why it's supposed to be
used.
Someone who knows how it *actually* works is encouraged to send a
better explanation.
diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
index 67425dc..3ad0fcd 100644
--- a/Documentation/git-format-patch.txt
+++ b/Documentation/git-format-patch.txt
@@ -12,6 +12,7 @@ SYNOPSIS
'git-format-patch' [-n | -k] [-o <dir> | --stdout] [--attach] [--thread]
[-s | --signoff] [--diff-options] [--start-number <n>]
[--in-reply-to=Message-Id]
+ [--ignore-if-in-upstream]
<since>[..<until>]
DESCRIPTION
@@ -78,6 +79,11 @@ OPTIONS
reply to the given Message-Id, which avoids breaking threads to
provide a new patch series.
+--ignore-if-in-upstream::
+ Do not include the same patch twice. If there are two commits
+ that would produce identical patches, the second one is
+ excluded from the output.
+
CONFIGURATION
-------------
You can specify extra mail header lines to be added to each
--
1.5.0.rc1.g04f3-dirty
--
David Kågedal
next reply other threads:[~2007-01-18 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 11:27 David Kågedal [this message]
2007-01-18 13:40 ` [PATCH] Document --ignore-if-in-upstream in git-format-patch Johannes Schindelin
2007-01-18 14:13 ` David Kågedal
2007-01-18 14:18 ` Johannes Schindelin
2007-01-19 16:58 ` 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=8764b4fuc8.fsf@morpheus.local \
--to=davidk@lysator.liu.se \
--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).