Re: On-branch topic description support?

On Thu, Jul 21, 2022 at 02:26:45PM -0400, Konstantin Ryabitsev wrote:

Hmm... well, it works great as long as you remember to always use --rebase-merges. The moment you forget to pass -r to "git rebase", your cover letter commit disappears, and I'm not sure this is going to work for what I am trying to do (which is to make the process of submitting patch series simpler). I know it's possible to configure git so that "git pull --rebase" preserves merges, but there doesn't appear to be a way to force "git rebase -i" to do the same without the -r flag. Also, "rebase -ir" looks really different when there is a tip merge commit, which will probably also be confusing to newbies just starting out with rebase workflows.

So, I'm not sure that at this time this is objectively "better" than keeping the cover letter in an empty commit at the start of the series. :-/

-K