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

Re: [PATCH] git-format-patch -3

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 18, 2007, 01:25 UTC
Message-ID
<Pine.LNX.4.63.0701180221010.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<7vk5zlqqum.fsf@assigned-by-dhcp.cox.net>
Hi,
On Wed, 17 Jan 2007, Junio C Hamano wrote:
>  * I think this is incompatible with --ignore-if-upstream, which
>    I haven't bothered to look into yet.
Uhm. What exactly _would_ be upstream?

At the moment, for "--ignore-if-in-upstream" we handle _only_ ranges (a..b), where we treat the left part as the upstream, so we first parse all the diffs in b..a, and then ignore all commits in a..b which have an already-seen diff hash.

However, if we want to do the logical analogue with "-22 HEAD", the equivalent to b..a would trivially contain no commits at all.

>    Likes, dislikes?
It sure is supported by the principle of least surprise.

Ciao, Dscho

Previous: Shawn O. Pearce
Message 8 of 8 in “git-format-patch -3”
  1. git-format-patch -3Junio C Hamano, Jan 17, 2007
  2. Add --summary to git-format-patch by defaultJunio C Hamano, Jan 17, 2007
  3. git-format-patch: make --binary on by defaultJunio C Hamano, Jan 17, 2007
  4. Changes to e-mailed patch handling in v1.5.0Junio C Hamano, Jan 17, 2007
  5. Andy ParkinsJan 18, 2007
  6. Brian GernhardtJan 18, 2007
  7. Shawn O. PearceJan 18, 2007
  8. Johannes SchindelinJan 18, 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.