On Sun, Aug 14, 2016 at 11:28 PM, Stefan Beller <sbeller@xxxxxxxxxx> wrote: > I would imagine this is similar to the pull requests on the linux > mailing list, i.e. > how it is with merges. Back in the time we did not open the editor for you to > talk about the merge you just did, and then we started doing that. > > So what to do when the description already exists? > > We could amend the description separated by a > > # comment, below was added: > > line or such and then open the editor asked for user input. > > Thanks, > Stefan > This is why my gut feeling is that we should instead have a separate way to store a cover letter, as it doesn't necessarily have to apply to a branch or a merge commit, but could just be annotation against a series of commits (maybe stored as base + tip, since most series would be linear in nature?) However, opening an editor and amending seems quite reasonable to me if we're just editing branch description, and then storing that as part of merge commit would be reasonable? I really think we want some alternative way to store it for other use cases besides the description, though. Regards, Jake -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html