Re: On-branch topic description support?

From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Date: Jul 21, 2022, 15:39 UTC
Message-ID: <20220721153955.lnfqfilri24i2yw6@meerkat.local>
In-Reply-To: <010101d89d16$a97184a0$fc548de0$@nexbridge.com>

On Thu, Jul 21, 2022 at 11:29:20AM -0400, rsbecker@nexbridge.com wrote:

Show 5 quoted lines

> I might be missing something here, but could not a description follow
> similar semantics to how git describe works on tags? Anchor the description
> on the commit where the branch was spawned, then determine the appropriate
> description based on things like --first-parent. Again, I'm probably in the
> weeds.

I think the trouble is that "commit where the branch was spawned" is not reliable due to:

- rebasing the work on a different branch
- reordering commits (including the first commit in the series)

This is the main reason why I actually want to stick the empty commit with the cover letter not at the tip of the branch, but at the start of the series, so as to clearly demarcate where the series of commits we're interested in starts (at least while the author is working on them -- when it sent off upstream that commit can get removed/moved).

-K