On Fri, Feb 11, 2022 at 05:25:49PM -0300, Alvaro Herrera wrote:
> > I'm not sure git diff --cherry-pick is widely known/used, but I think
> > using that relative to master may be good enough.
>
> I had never heard of git diff --cherry-pick, and the manpages I found
> don't document it, so frankly I doubt it's known. I still have no idea
> what does it do.
See git-log(1)
--cherry-pick
Omit any commit that introduces the same change as another commit on
the “other side” when the set of commits are limited with symmetric difference.
The "symmetric difference" is the triple-dot notation.
The last few years I've used this to check for missing bits in the draft
release notes. (Actually, I tend to start my own list of features before
that). It's doing a generic version of what git_changelog does.
https://www.postgresql.org/message-id/20210510144045.gc27...@telsasoft.com
> I suppose there is an obvious reason why using git diff with
> $(git merge-base ...) as one of the arguments doesn't work for these purposes.
>
> > Andres thinks that does the wrong thing if CI is run manually (not by CFBOT)
> > for patches against backbranches.
>
> I wonder if it's sufficient to handle these things (coverage
> specifically) for branch master only.
Or default to master, and maybe try to parse the commit message and pull out
Backpatch-through: NN. It's intended to be machine-readable, after all.
Let's talk about it more on the/another thread :)
--
Justin
