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

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

From
Eric Miao <eric.y.miao@gmail.com>
Date
Nov 5, 2012, 02:26 UTC
Message-ID
<CAMPhdO_33CPJv2hAvPuJ10KZ7v_fgP9P2kV_WLVK2tapjQQ5=A@mail.gmail.com>
Hi All,

Does anyone know if git has sort of support for a series of patches, i.e. a patchset or changeset? So whenever we know the SHA1 id of a single patch/commit, we know the patchset it belongs to. This is normal when we do big changes and split that into smaller pieces and doing only one simple thing in a single commit.

This will be especially useful when tracking and cherry-picking changes, i.e. monitoring on the changes of some specific files, and if a specific patch is interesting, we may want to apply the whole changeset, not only that specific one.

Ideas?
- eric
Next: Michael J Gruber
Message 1 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.