Date: Wed, 13 Nov 2019 17:28:59 +0100 From: Ilya Bakulin <ilya@bakulin.de> To: Ed Maste <emaste@freebsd.org> Cc: freebsd-git@freebsd.org Subject: Re: FYI - LLVM migration to Git and GitHub has started Message-ID: <CADzbx%2BqQrXrzvOS=Rpww7NmW4xosmDc8HA%2B-ML8JxfFtPXG6%2BQ@mail.gmail.com> In-Reply-To: <CAPyFy2Aaovca5B0D0cyo3r0%2B7%2BS4CK%2BnhmfuY4V1fLmjvJ49dQ@mail.gmail.com> References: <CAPyFy2Aaovca5B0D0cyo3r0%2B7%2BS4CK%2BnhmfuY4V1fLmjvJ49dQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
So with that new Github feature in mind, if we all move FreeBSD main repo to Github tomorrow, what will break for us? What does Github not give us that we absolutely need? On Tue, Oct 22, 2019 at 6:45 PM Ed Maste <emaste@freebsd.org> wrote: > From the llvm development mailing list: > > > We're getting ready to start migrating to GitHub. SVN will be > > moved to read-only now and we'll > > begin the process of turning on GitHub commit access. > http://lists.llvm.org/pipermail/llvm-dev/2019-October/136106.html > > A few additional points I found in another thread that are probably of > interest to the FreeBSD/git community: > > > 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. > http://lists.llvm.org/pipermail/llvm-dev/2019-October/135912.html > > and later: > > GitHub only supports pre-receive hooks in their Enterprise Server > edition, > > which isn't a good option for us, because we would need to self-host it. > _______________________________________________ > freebsd-git@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-git > To unsubscribe, send any mail to "freebsd-git-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADzbx%2BqQrXrzvOS=Rpww7NmW4xosmDc8HA%2B-ML8JxfFtPXG6%2BQ>