[llvm-dev] [cfe-dev] How soon after the GitHub migration should committing with git-llvm become optional?

Hubert Tong via llvm-dev llvm-dev at lists.llvm.org
Tue Oct 15 12:26:04 PDT 2019


On Tue, Oct 15, 2019 at 3:47 AM Marcus Johnson via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> I say retire it instantly.
>
+1. It has never been a real requirement to use the script. Using native
svn is still viable until the point of the migration.


>
> > On Oct 15, 2019, at 3:14 AM, Tom Stellard via cfe-dev <
> cfe-dev at lists.llvm.org> wrote:
> >
> > ´╗┐Hi,
> >
> > I mentioned this in my email last week, but I wanted to start a new
> > thread to get everyone's input on what to do about the git-llvm script
> > after the GitHub migration.
> >
> > The original plan was to require the use of the git-llvm script when
> > committing to GitHub even after the migration was complete.
> > The reason we decided to do this was so that we could prevent developers
> > from accidentally pushing merge commits and making the history
> non-linear.
> >
> > Just in the last week, the GitHub team completed the "Require Linear
> > History" branch protection, which means we can now enforce linear
> > history server side and do not need the git-llvm script to do this.
> >
> > With this new development, the question I have is when should the
> > git-llvm script become optional?  Should we make it optional immediately,
> > so that developers can push directly using vanilla git from day 1, or
> should we
> > wait a few weeks/months until things have stabilized to make it optional?
> >
> > Thanks,
> > Tom
> >
> >
> >
> >
> >
> > _______________________________________________
> > cfe-dev mailing list
> > cfe-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191015/747fc2a9/attachment.html>


More information about the llvm-dev mailing list