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

[Joerg Sonnenberger via cfe-dev]

On Fri, Mar 22, 2019 at 04:39:26PM +0000, David Greene via llvm-dev wrote:
> One consequence of this is that release branches can be more easily
> validated.  In a world with merge commits, many projects make fixes on
> the release branch *first*, then merge the release branch to master,
> ensuring that fixes in the current release make it into the next release
> (when that is branched off master in the future).

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.

Joerg