On Sun, Nov 23, 2014, at 01:25, Nick Coghlan wrote: > On 23 November 2014 at 16:03, Donald Stufft <donald at stufft.io> wrote: > >> On Nov 23, 2014, at 12:59 AM, Nick Coghlan <ncoghlan at gmail.com> wrote: > >> > >> Note that if folks prefer Git, BitBucket supports both. I would object > >> strongly to unilaterally forcing existing contributors to switch from > >> Mercurial to git. > > > > Going to all the trouble to move to an external repository and choosing the > > least popular option out of the two main ones seems like a bad idea in > > general. > > Moving repos from hg.python.org to bitbucket.org is just a matter of > switching some URLs around, and changing some backend systems to cope > with the new location. The end result should be to make life better > for existing contributors *and* new contributors using the web UI, and > be largely transparent to folks using command line tools. > > By contrast, proposals to switch from Mercurial to Git impose a > *massive* burden on contributors that don't already know git. But how many people are there who will have this massive burden imposed on them? I imagine there's few among us who haven't had to learn git for our job or other projects.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4