Earlier quoted context omitted.
I meant "git reset --hard" as a prefix for useful . Can hg set the current branch to point anywhere in time? Does histedit do exactly what "rebase" does? Does it also work with "--onto" and other rebase features?
hg branches are entirely different from git branches, so resetting them in that way doesn't make sense. The closest approximation - bookmarks - can indeed be reset (hg bookmark -f). histedit does a variety of things; I'm not sure if it covers all of rebase's branches. Mercurial does also have a rebase facility now as well.
Python now uses Mercurial
101–110 of 114 posts
Re: Python now uses Mercurial
#102Git and Hg accomplish essentialy the same thing. The platform support and tool/utility support for Mercurial on windows in important to note. I decided to choose Mercurial as the VCS for my 'work'. This was a team that had no prior exposure to VC before. And works in a mixed environment. Hg follows the 'one true way' philosophy of Python; so there's just a single command to learn for each task. Plus, Bitbucket's new…
This is basically where I stand as well. Git has no real appeal for me, but GitHub does. Plus, with the ridiculously easy hg-git[1] tool, I'm able to take advantage of GitHub while staying in my Hg comfort zone :) [1]: http://hg-git.github.com/
I often hear people claiming hg is easier to use and has a better interface, but every time I have to use hg it rubs me the wrong way because I can't use it like I use git :/ (In particular, I find hg branches needlessly complicated and cumbersome compared to git's "just a pointer" model)
I guess between the two you'll end up using the one you first bother to learn beyond memorising basic commands.
Re: Python now uses Mercurial
#103Earlier quoted context omitted.
This is basically where I stand as well. Git has no real appeal for me, but GitHub does. Plus, with the ridiculously easy hg-git[1] tool, I'm able to take advantage of GitHub while staying in my Hg comfort zone :) [1]: http://hg-git.github.com/
Heh, I'm the exact opposite. I use a hg-to-git tool to access hg repositories, because I'm much more comfortable with git. I often hear people claiming hg is easier to use and has a better interface, but every time I have to use hg it rubs me the wrong way because I can't use it like I use git :/ (In particular, I find hg branches needlessly complicated and cumbersome compared to git's "just a pointer" model) I guess…
Re: Python now uses Mercurial
#104Earlier quoted context omitted.
octopus merges are rare in the git.git repo: $ git rev-list --merges --parents --tags | awk '{print (NF-1)}' | sort | uniq -c 4409 2 22 3 5 4 3 5 1 6 So there's been a total of 31 octopus merges compared to 4409 typical two-parent merges.
On the other hand, roughly an entire 2% of merges on linus's linux tree have been octopus merges. Hardly something to scoff at. 5 10 6 11 5 12 3 13 2 14 1 18 14592 2 1 20 1 21 1 24 129 3 1 30 50 4 25 5 21 6 13 7 18 8 7 9
Re: Python now uses Mercurial
#105Git and Hg accomplish essentialy the same thing. The platform support and tool/utility support for Mercurial on windows in important to note. I decided to choose Mercurial as the VCS for my 'work'. This was a team that had no prior exposure to VC before. And works in a mixed environment. Hg follows the 'one true way' philosophy of Python; so there's just a single command to learn for each task. Plus, Bitbucket's new…
Why would you choose Github over Bitbucket for your FOSS projects? I haven't used Bitbucket yet, so I'm interested in a comparison.
Re: Python now uses Mercurial
#106Re: Python now uses Mercurial
#107Earlier quoted context omitted.
This is basically where I stand as well. Git has no real appeal for me, but GitHub does. Plus, with the ridiculously easy hg-git[1] tool, I'm able to take advantage of GitHub while staying in my Hg comfort zone :) [1]: http://hg-git.github.com/
Heh, I'm the exact opposite. I use a hg-to-git tool to access hg repositories, because I'm much more comfortable with git. I often hear people claiming hg is easier to use and has a better interface, but every time I have to use hg it rubs me the wrong way because I can't use it like I use git :/ (In particular, I find hg branches needlessly complicated and cumbersome compared to git's "just a pointer" model) I guess…
Re: Python now uses Mercurial
#108Earlier quoted context omitted.
PHP + ...SVN? Gotta say, they deserve each other.
and OpenCOBOL uses CVS http://www.opencobol.org/ ( http://sourceforge.net/projects/open-cobol/develop ) maybe a language older than that still uses RCS
I've checked files out that were last modified before I was born.
Re: Python now uses Mercurial
#109Earlier quoted context omitted.
hg histedit, hg revert, hg update -r{any revspec}
I meant "git reset --hard" as a prefix for useful . Can hg set the current branch to point anywhere in time? Does histedit do exactly what "rebase" does? Does it also work with "--onto" and other rebase features?
There are a few limitations to `histedit` compared to `git rebase -i` I think: I believe it's possible to split revisions using `rebase -i`, I don't think that can be done using histedit (it has pick, edit, drop and fold). Histedit also misses the (pretty recent I believe) `exec` action of git's rebase -i.
Re: Python now uses Mercurial
#110Earlier quoted context omitted.
I meant "git reset --hard" as a prefix for useful . Can hg set the current branch to point anywhere in time? Does histedit do exactly what "rebase" does? Does it also work with "--onto" and other rebase features?
hg branches are entirely different from git branches, so resetting them in that way doesn't make sense. The closest approximation - bookmarks - can indeed be reset (hg bookmark -f). histedit does a variety of things; I'm not sure if it covers all of rebase's branches. Mercurial does also have a rebase facility now as well.
That is correct. In Mercurial, git's `rebase` is (sensibly, as far as I am concerned) split into two different commands: `histedit` handles the history edition within a branch and `rebase` handles the rebasing of a branch on a revision of an other branch.