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

Re: Support for a series of patches, i.e. patchset or changeset?

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Nov 5, 2012, 14:40 UTC
Message-ID
<5097CFCB.7090506@drmicha.warpmail.net>
In-Reply-To
<CAMPhdO-1ar52QGuSzbyFBSKMf48fDb6Bbxw5u3PCuVYxkO2=3w@mail.gmail.com>
Eric Miao venit, vidit, dixit 05.11.2012 15:12:
> The problem is, most cases we have no idea of the base rev1, and commit rev2
> which it's leading up to. E.g. for a single patch which is between
> commit rev1..rev2,
> how do we find out rev1 and rev2.

So, then the question is: What do you know/have? Is your patch the output of "git format-patch", "git diff", or just some sort of diff without any git information?

Michael
Previous: Eric MiaoNext: Eric Miao
Message 4 of 13 in “Support for a series of patches, i.e. patchset or changeset?”
  1. Eric MiaoNov 5, 2012
  2. Michael J GruberNov 5, 2012
  3. Eric MiaoNov 5, 2012
  4. Michael J GruberNov 5, 2012
  5. Eric MiaoNov 6, 2012
  6. Johannes SixtNov 6, 2012
  7. Eric MiaoNov 6, 2012
  8. Johannes SixtNov 6, 2012
  9. Eric MiaoNov 7, 2012
  10. Jeff KingNov 8, 2012
  11. Eric MiaoNov 9, 2012
  12. Enrico WeigeltNov 10, 2012
  13. Eric MiaoNov 10, 2012

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.