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

Re: One question about git-format-patch

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 19, 2013, 23:06 UTC
Message-ID
<CAPc5daW6ohYxJP0eyfW0DT_Q-E8v0quweRBwJCAZOVrEMWchjA@mail.gmail.com>
In-Reply-To
<804161F448B352478D7503429A0B7F27CA94AC@ex10-mbx-36002.ant.amazon.com>
> I’m a git user, and recently I’ve noticed there’re some differences between
> “$ git format-patch –n” and “$ git format-patch HEAD~n”. According to the
> documentation: “-<n> Prepare patches from the topmost <n> commits.”

Correct. However, HEAD~n will prepare patches for commits that are not ancestor of HEAD~n.

And there may well be a lot more than n such commits, unless you are working on a strictly linear history.

Next: Junio C Hamano
Message 1 of 2 in “Re: One question about git-format-patch”
  1. Junio C HamanoJul 19, 2013
  2. Junio C HamanoJul 20, 2013

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.