On Wed, Jul 3, 2013 at 9:18 PM, Gerlando Falauto <[email protected]> wrote:
> While I appreciate the features described in the tutorial, I was > wondering if the few missing pieces in this whole process could be > taken care of somehow: cover letters, revision changes and recipient > lists. This kind of information is intimately related to a patch > series, though it's not stored within the GIT repo, and you > more-or-less have to dig to find (perhaps from your inbox or from a > local copy of the messages you sent) and re-type this stuff every > time you resubmit. I find this very, very frustrating. > > I would really love to be able to store this kind of information > within my git repo, so that every time I make a change as a result > of external feedback, I can simply JUST EDIT the cover letter, the > commit messages and the associated metadata (like revision history). > Then I only have to type ONE command to re-submit. > > Am I dreaming? Am I the only one with this problem? Or am I in the > wrong room? > > I am more than willing to implement this myself, if someone just > points me in the right direction. No, that sounds like a perfectly reasonable feature to add to StGit (and one I'd use myself, on occasion). The only complicating factor I can think of is that an StGit stack might contain more than one patch series, so we'd need a way to store more than one cover letter, and thus a way to tell which patches go with which cover letter. One design that leaps to mind is to use empty patches for cover letters (with special headers in the commit message to mark it as a cover letter and to store the recipient list), and let each cover letter apply to the patches following it, until the end of the stack or the next cover letter. Catalin, do you have an opinion? -- Karl Wiberg, [email protected] subrabbit.wordpress.com www.treskal.com/kalle _______________________________________________ stgit-users mailing list [email protected] https://mail.gna.org/listinfo/stgit-users
