git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Document --ignore-if-in-upstream in git-format-patch

From
David Kågedal <davidk@lysator.liu.se>
Date
Jan 18, 2007, 11:27 UTC
Message-ID
<8764b4fuc8.fsf@morpheus.local>
---
 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: Johannes Schindelin
Message 1 of 5 in “Document --ignore-if-in-upstream in git-format-patch”
  1. Document --ignore-if-in-upstream in git-format-patchDavid Kågedal, Jan 18, 2007
  2. Johannes SchindelinJan 18, 2007
  3. David KågedalJan 18, 2007
  4. Johannes SchindelinJan 18, 2007
  5. Junio C HamanoJan 19, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.