Re:Bitbucket Pipelines Beta: continuous delivery inside Bitb...
by ngoldbaum on Tuesday May 24, 2016 @03:10PM
(#11764603)
I prefer mercurial over git and will choose it every time for new projects unless there's some other concern preventing that.
Mercurial has a number of features that git never implemented - in particular revsets. I also prefer the hg CLI over the git CLI. Mercurial has sane, concise online help, and a lot of work went into the design of the command-line to be consistent, composable, and made of pieces that do one thing and do it well.
Re:Bitbucket Pipelines Beta: continuous delivery inside Bitb...
by rjbwork on Tuesday May 24, 2016 @03:21PM
(#11764703)
Seconding this sentiment. Far, far, prefer hg to git. TortoiseHg blows away the Git UI's as well, IMO. I always feel like i'm poking around in the dark on SourceTree.
Re:Bitbucket Pipelines Beta: continuous delivery inside Bitb...
by kasey_junk on Tuesday May 24, 2016 @12:03PM
(#11762660)
I do, assuming its just for me. I still much prefer the hg cli over git.
But, I'll grant its not worth fighting over if I am working with collaborators who have a git preference.
Re:Bitbucket Pipelines Beta: continuous delivery inside Bitb...
by tachion on Tuesday May 24, 2016 @01:04PM
(#11763294)
I really like to ask, if someone has Git preference, or is Git the only thing they know, enforcing VCS === Git point of view on everyone around...
Re:Bitbucket Pipelines Beta: continuous delivery inside Bitb...
by brianwawok on Tuesday May 24, 2016 @02:48PM
(#11764418)
Kasey, it is "origin/master" or "origin master"? Ha ha
Have used both, they are so close, seems "odd" to go for the way less popular one, barring you have a really old HG repo and haven't bothered to switch.