On Tue, Jan 29, 2019 at 5:33 PM Tom Stellard via lldb-dev <email@example.com> wrote: > > Hi, > > As part of the migration of LLVM's source code to github, we need to update > our developer policy with instructions about how to interact with the new git > repository. There are a lot of different topics we will need to discuss, but > I would like to start by initiating a discussion about our merge commit > policy. Should we: > > 1. Disallow merge commits and enforce a linear history by requiring a > rebase before push. > > 2. Allow merge commits. > > 3. Require merge commits and disallow rebase before push. > > I'm going to propose that if we cannot reach a consensus that we > adopt policy #1, because this is essentially what we have now > with SVN. > > What does everyone think?
I'm strongly in favour of #1: no merges allowed, enforced by the upstream repository, and that for release branches we use cherry-picks like we do currently. Thanks, Hans _______________________________________________ lldb-dev mailing list firstname.lastname@example.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev