Re: [kernel.org users] b4: encouraging using the cover letter in merge commits?

["Michal Kubeček" <mkubecek@suse.cz>]

On Mon, Dec 21, 2020 at 03:05:52PM -0400, Jason Gunthorpe wrote:
> My biggest problem with the cover letters is while the are in the
> repository, someplace, I've never actually found one while hunting
> around in the git history for clues, eg with 'git blame' or 'git log
> log -p'
> 
> In fact more often than not I find the netdev cover letters through
> hunting in lore, not through git.
> 
> Is there some git sequence to make it visible?
> 
> The Link header is a nicer because no matter how I end up at a commit
> I can go back to an email discussion..

If you have a commit in merged branch, the corresponding merge commit
should be the last shown by

  git rev-list --ancestry-path --merges --topo-order --pretty=full \
      ${id}..${branch}

Or first if you also add "--reverse". Unfortunately "-n 1" cannot be
used to show just that merge commit as it would be applied to the list
before "--reverse".

In a script, you could either postprocess the output with sed or count
the merge commits first:

  count=$(git rev-list --ancestry-path --merges --topo-order \
      "${id}..${branch}" | wc -l)
  git rev-list --ancestry-path --merges --topo-order --skip $[count - 1] \
      --pretty=full "${id}..${branch}"

Michal