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

Re: [ANNOUNCE] git-series: track changes to a patch series over time

From
Josh Triplett <josh@joshtriplett.org>
Date
Aug 1, 2016, 18:37 UTC
Message-ID
<20160801183750.ivwue4mxm5ilgzqz@x>
In-Reply-To
<b7bd1464-1412-1feb-fe10-9ecb6018e122@wwwdotorg.org>
On Mon, Aug 01, 2016 at 09:14:54AM -0600, Stephen Warren wrote:
Show 14 quoted lines
> On 07/29/2016 12:40 AM, Josh Triplett wrote:
> > I'd like to announce a project I've been working on for a while:
> > 
> > git-series provides a tool for managing patch series with git, tracking
> > the "history of history". git series tracks changes to the patch series
> > over time, including rebases and other non-fast-forwarding changes. git
> > series also tracks a cover letter for the patch series, formats the
> > series for email, and prepares pull requests.
> 
> Just as an FYI, I wouldn't be surprised if there's some overlap, or
> potential for merging of tools, between this tool and the "patman" tool
> that's part of the U-Boot source tree:
> 
> http://git.denx.de/?p=u-boot.git;a=blob;f=tools/patman/README;h=e36857dedea1d0dbafa41732aaf9bf0988d63f38;hb=HEAD
Interesting tool; thanks for the link.

As far as I can tell from that documentation, patman doesn't track old versions of a patch series; you rebase to modify patches or change patman tags (embedded in commit messages), and nothing preserves the previous version. And it tracks the cover letter and similar in one of the commit messages in the series, so previous versions of that don't get saved either. If you wanted to track the history of your changes, you'd have to use branch names or similar.

In addition, tracking metadata in commit messages only works with a patches-by-mail workflow where the messages get processed when generating patches; that doesn't work for please-pull workflows.

patman does have quite a few interesting ideas, though. git-series needs some way of handling To/Cc addresses for patches and the cover letter (beyond just scripts/get_maintainer.pl), and more automatic handling of series versioning (v2, v3, ...) and associated series changelogs. Suggestions welcome.

- Josh Triplett
Previous: Stephen WarrenNext: Simon Glass
Message 15 of 23 in “[ANNOUNCE] git-series: track changes to a patch series over time”
  1. Josh TriplettJul 29, 2016
  2. Richard IpsumJul 29, 2016
  3. Josh TriplettJul 29, 2016
  4. Richard IpsumJul 29, 2016
  5. Josh TriplettJul 29, 2016
  6. Richard IpsumJul 31, 2016
  7. Stefan BellerJul 29, 2016
  8. Richard IpsumJul 31, 2016
  9. Christian CouderAug 1, 2016
  10. Eric WongAug 1, 2016
  11. Josh TriplettAug 1, 2016
  12. Richard IpsumAug 1, 2016
  13. Eric WongAug 1, 2016
  14. Stephen WarrenAug 1, 2016
  15. Josh TriplettAug 1, 2016
  16. Simon GlassAug 15, 2016
  17. Josh TriplettAug 15, 2016
  18. Richard IpsumAug 3, 2016
  19. Josh TriplettAug 4, 2016
  20. Richard IpsumAug 10, 2016
  21. Josh TriplettAug 10, 2016
  22. Eric WongAug 11, 2016
  23. Jakub NarębskiAug 24, 2016

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.