[cfe-dev] [llvm-dev] [lldb-dev] [GitHub] RFC: Enforcing no merge commit policy

[David Greene via cfe-dev]

Andrea Bocci via cfe-dev <cfe-dev at lists.llvm.org> writes:

> On Fri, 22 Mar 2019 at 23:41, Joerg Sonnenberger via cfe-dev <cfe-dev at lists.llvm.org> wrote:
>
>  This always felt strongly like a design deficit of git and not a feature
>  that should be advertised. That is, lack of proper cherry-picking meta
>  data is the main bug and the back-way model of committing to the oldest
>  release branch first is the consequence.
>
> git cherry-pick -x  will append a line that says "(cherry picked from commit ...)" to the original commit message in order to indicate which commit this change was
> cherry-picked from.
>
> It is not "metadata", but could serve the same purpose.

Yes, and I'm sure there are tools external to git that can use that
information, but AFAIK git itself does not have a way to make 'git
branch --contains' take such information into account.  It is indeed a
shortcoming of git.

                        -David