{"thread":{"id":"36694","subject":"[ANNOUNCE] git send-series v0.1","startedAt":"2014-05-19T00:37:43Z","lastAt":"2014-05-19T00:37:43Z","messageCount":1,"participants":["Felipe Contreras"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"242137","messageId":"537952579dba1_10da88d308ed@nysa.notmuch","threadId":"36694","inReplyTo":null,"subject":"[ANNOUNCE] git send-series v0.1","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2014-05-19T00:37:43Z","receivedAt":"2014-05-19T00:37:43Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Hi,\n\nThis tool allows you to maintain a patch series more easily. You can store the\ncover letter, the cc list, version of the series, and other metadata.\n\nBy default it will use the currently checked out branch, and show you a\ntemplate like this:\n\n------------\nversion:\ncc:\n\nSubject\n\nContent.\n------------\n\nThe first part is a YAML document with all optional fields, such as 'version',\n'cc', 'to'. You can store any information you want using the YAML syntax.\n\nThe second part, delimited by a blank line, is the cover letter. The first like\nwill be used as the subject of the cover letter email, and the rest as the\ncontent 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 an the\nother.\n\nEnjoy.\n\nhttps://github.com/felipec/git-send-series\n\n-- \nFelipe Contreras\n"}]}