Date: Mon, 23 Sep 2019 10:51:33 -0700 From: Sean Chittenden <sean@chittenden.org> To: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= <uspoerlein@gmail.com> Cc: freebsd-git@freebsd.org Subject: Re: Service disruption: git converter currently down Message-ID: <CAHevUJHwDet8pBdrE4SN3nuoAUgP-ixpCz9uOTdwbE31UDDsbA@mail.gmail.com> In-Reply-To: <CAJ9axoR2VXFo9_hx9Z1Qwgs7U-dkan56hrUKO9f7uN6Wpd15xQ@mail.gmail.com> References: <CAJ9axoR41gM5BGzT-nPJqqjym1cPYv31dDUwXwi4wsApfDJW%2Bw@mail.gmail.com> <CAJ9axoToynYpF=ZdWdtn_CkkA2nVkgtckQSu%2BcMis1NOXgUdnA@mail.gmail.com> <CAJ9axoR2VXFo9_hx9Z1Qwgs7U-dkan56hrUKO9f7uN6Wpd15xQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Please note however, that more "garbage" metadata escaped from SVN into > github, meaning 3rd parties have a hard time re-running the conversion and > making sure that it matches SVN down to the metadata (i.e. timestamps). > > Eventually, this will have to be re-rolled and a new "master" branch will > be force-pushed into github. There's no timeline for this yet. > Wait, what? Can you elaborate? Discussion of a force-push to github has occurred a few times and been explicitly ruled out because most of our corporate citizens use github to integrate changes from FreeBSD. Rerolling master was universally rejected when we socialized wanting to do this due to the level of disruption this would cause. The feedback was that this would be a high-cost, low-value operation. In the tradeoffs of purity vs pragmatism, pragmatism wins every time (that is the FreeBSD way). -sc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHevUJHwDet8pBdrE4SN3nuoAUgP-ixpCz9uOTdwbE31UDDsbA>