3 ms·
I do. I'm a long term user of mercurial for my own projects. I was also an advocate for moving to git in our organisation, but it doesn't fit. One hammer is no
by hp50g 14y ago
I do. I'm a long term user of mercurial for my own projects. I was also an advocate for moving to git in our organisation, but it doesn't fit.
One hammer is not necessarily good for all nails.
- Volpe 14y agoI'm sorry with the poor assumption... But you started this thread with "Github downtime is the reason we can't use git internally" <--- This illustrates either you don't understand git very well. OR you don't understand logic very well.... I was giving you the benefit of the doubt on the latter... :\
- pifflesnort 14y agoHow, exactly, do you propose the following things to work if GitHub is down? - Pull requests and code reviews - Automatic integration builds of all checkins - Commit notifications via e-mail - Browsing of sources via the web - Sharing of code between collaborating users DVCS may be "distributed", but organizations and user collaboration are not.
- jiggy2011 14y agoNone of that stuff is exclusive to github.
- nitrogen 14y agoThe would work exactly how they work with the Linux kernel, for which git was created.
- pifflesnort 14y agoYes, via centralized mailing lists and collaboration infrastructure.
- Volpe 14y ago... None of that stuff requires github. How about also have the code on bitbucket (if you want to use flashy web services). Chances of them going down at the same time seems remote.
- hp50g 14y agoActually its more likely that they're both unavailable than one is I.e our pipe goes down. Another reason to do it in house.