{"thread":{"id":"54915","subject":"[ANN] git-send-series 1.0","startedAt":"2021-01-01T03:58:04Z","lastAt":"2021-01-01T03:58:04Z","messageCount":1,"participants":["Felipe Contreras"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"413289","messageId":"5fee9c3f91cb5_988208fb@natae.notmuch","threadId":"54915","inReplyTo":null,"subject":"[ANN] git-send-series 1.0","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-01-01T03:51:27Z","receivedAt":"2021-01-01T03:58:04Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Hello,\n\nI have a bunch of patch series flying around, and it gets tedious to\nkeep track of the state of each one of them. That's why I created\n`git send-series`; a tool to keep track of multiple patch series.\n\nThe idea is simple; a patch series contains certain metadata (version,\ncc list, subject, body) that should be easy to edit, and other metadata\nsuch as the previous version's range (branch@{u}..branch), can be be\nautomatically tracked.\n\n`git send-series` does all that for you.\n\nThe format of the metadata file is straightforward:\n\n------------\nversion: 2\ncc:\n  - Felipe Contreras <felipe.contreras@gmail.com>\n  - Don Draper <don@draper.me>\n  - William G. Connolly <william@connolly.me>\n\nREADME: bunch of fixes\n\nThere was a bunch of typos and grammatical errors.\n\nI've separated the fixes in multiple patches.\n------------\n\nThe first part is a YAML document with all optional fields, such as 'version',\n'cc', 'to'. The second part--delimited by a blank line--is the cover\nletter. The first like will be used as the subject of the cover letter\nemail, and the rest as the content of the email.\n\nThen standard tools will be used to send the emails: `git format-patch` and\n`git send-email`, which you must have configured before using this helper.\n\nIn the end, a custom ref will be created to save the current state of the\nbranch. For example, if you want to see what was the status of your series of\nthe branch 'feature-a' in version 2, you can use 'sent/feature-a/v2', for\nexample to create an interdiff to see what changed between one version and the\nother.\n\nBy default `git send-email` will attach a range-diff to the cover-letter\nusing the previous version of the series.\n\nThe last version (0.1) was a very crude attempt (although it did work),\nnow it's a much more mature tool I've been constantly testing and\nimproving over the past few months.\n\nChanges since the last version:\n\n * Add range-diff with the last range sent\n * Add safety to make sure the same version isn't sent twice\n * Add --dry-run option\n * Add --show option (to show the cover-letter before sending)\n * Add --range-diff option (to show the range-diff that will be sent)\n * Add --delete option (to remove all the branch metadata)\n * Add safety that the upstream tracking branch is configured\n * Add manpage documentation\n * Add vim syntax\n * Improve installation (make install works now)\n * Allow arrays in the YAML header (cleaner Cc list)\n * Check exit status of the editor (e.g. :cq in vim)\n * Chomp the last newlines of the body\n * Clean the patches directory properly\n * Fix in the check for the current branch\n\nA screenshot of how it looks on the wild (with the vim syntax) [1]:\n\nEnjoy and Happy New Year!\n\nhttps://github.com/felipec/git-send-series\n\n[1] https://snipboard.io/ExfbWo.jpg\n\n-- \nFelipe Contreras\n"}]}