Re: On-branch topic description support?

[Konstantin Ryabitsev <konstantin@linuxfoundation.org>]

On Wed, Jul 20, 2022 at 10:25:19PM -0700, Elijah Newren wrote:
> Seems mostly reasonable, but I'm curious about one thing:
> 
> The cover letter material often includes stuff that would not make
> sense for the merge message (e.g. "Rebased this version on master
> because of conflicts with ...", "Changes since v3", "I'm a little
> unsure of the logic in Patch 5", "Patch 3 might be controversial; take
> a look", etc.)  Would there be some kind of syntax for specifying the
> part of the cover letter meant to be used in the merge commit message,
> or would we just start out with it pre-populating the commit message
> and expect the integrator to cull out the irrelevant parts?

Maybe reuse the scissors line, but throw away stuff after the scissors? E.g.:

    Subject: [PATCH v2 0/3] Implement foo

    This implements foo that is needed to...
    ...
    ...
    ...

    Signed-off-by: De Veloper <dev@example.com>
    Link: https://example.com/foo

    -- >8 --

    Note: I'm not sure about....

    ---

    Changes in v2:
     - Rewrote using libfoo
     - ...

    ---
    Diffstat, range-diff, etc.

    ---
    base-commit: abcde
    change-id: abcde-foobarbaz

-K