Re: storing cover letter of a patch series?
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Aug 16, 2016, 06:45 UTC
- Message-ID
- <CACsJy8DJmONcgQO37Xk+2cZb+Svx-bgwjrG1XrZQ4BYipownqw@mail.gmail.com>
- In-Reply-To
- <CA+P7+xr+HonJTj5AcRhAMf5Z059zHKiuOY8Zbd77uu_jAiiZBA@mail.gmail.com>
On Tue, Aug 16, 2016 at 12:26 PM, Jacob Keller <jacob.keller@gmail.com> wrote:
Show 14 quoted lines
>>> They can just add "squash! cover! <series>" commits for that ;-) Though more >>> likely the advanced workflow would be used... We'll need both (more than >>> one) options. >> >> Or even better, "git commit --reword $SHA1" brings up the editor with >> commit message of $SHA1. Modify any way you want and it creates a new >> empty, "reword!" commit that contains the diff between the old commit >> message and the new one. "reword!" can be consumed by "rebase -i >> --autosquash" without bringing up the editor again. I realize making >> "git commit --reword" run multiple times would be tricky though... > > I was just thinking you write text and it gets appended to the text of > the reworded commit, and when you squash them using rebase you get to > finalize it like a normal squash?
I think that's what Phillip meant by 'squash! cover!' though I wanted to go further, I don't want an editor popping up at rebase time, instead 'rebase' just update cover letter automatically for me.
-- Duy