It would certainly make it easier for me to contribute; not that I've had that much to contribute recently, but git is in my fingers now and I have to remind myself how to do things in hg.
On Mon, May 9, 2016 at 1:13 PM, Bill Deegan <[email protected]> wrote: > All, > > So it sounds like (from limited consensus), that switching to Git now, > would remove a significant barrier to contributing code/fixes? > > -Bill > > On Mon, May 9, 2016 at 8:12 AM, Tim Jenness <[email protected]> wrote: > >> >> > On May 9, 2016, at 07:57 , Rob Boehne <[email protected]> wrote: >> > >> > For me, scons is the ONLY project I work on that uses Mercurial, and >> > having to translate each and every command is a real pain. >> > I¹ve also NOT contributed back many changes I¹ve made to get Python to >> > build properly on old UNIX systems, primarily because it was using Hg. >> > >> > I doubt I¹m alone in this, and I¹m certain it¹s a lot easier to find a >> > competent developer who knows Git but has never used Mercurial than the >> > other way around. This is an extra effort for most developers, and that >> > extra effort will get more common, and more painful as the years go by. >> > IMHO switching to Git is a clear win. >> > >> >> I have to agree. Whilst I am really interested in helping with the python >> 3 port the hg hurdle has just meant I haven’t found the time. I have too >> many other things pulling at me that I can do easily with my git workflow. >> >> — >> Tim Jenness >> >> _______________________________________________ >> Scons-dev mailing list >> [email protected] >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> > > > _______________________________________________ > Scons-dev mailing list > [email protected] > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > -- Gary
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
