Previously, Mercurial revisions were stored as revision numbers (e.g. the tenth commit is stored as

Top Posts Announcing git-fc; a friendly fork of Git The problem with GNOME 3 Mercurial vs Git; it's all in the branches Bridge support in git for mercurial and bazaar Advanced running shoes Git concepts; the upstream tracking branch After two weeks of using GNOME 3, I officially hate it What it takes to improve running shoes Git or: How I fixed zsh completion Installing scratchbox 1 and 2 for ARM cross-compilation Setting up QEMU with a NAT git send-email tricks Twitter running shoes Updates Announcing git-fc; a friendly fork of Git wp.me/pgj4-qq 4 days ago I got a copy of Four Horsemen, I liked it, but not for everybody. Watch if you want something intellectual: buy.fourhorsemenfilm.com 2 weeks ago running shoes The Linux way; never ever break user experience. wp.me/pgj4-na 3 weeks ago New post: Advanced running shoes Git concepts; the upstream running shoes tracking branch: wp.me/pgj4-pi 2 months ago @ heviosso Wow. I think if any GNOME developer commits a crime, that's all right for them, because there's evidence running shoes to claim insanity. 2 months ago Recent Comments RexC on The Linux way; never ever break user experience whyIsthisneeded? on Announcing git-fc; a friendly fork of Git Eric Espino on The problem with GNOME 3 Michael Rhea on The problem with GNOME 3 Michael Rhea on The problem with GNOME 3
Git is able to find out and report if a branch is new, if it needs to be updated, if it can be fast-forward running shoes or not, etc. b3f6f3a..c0d1c89 master -> master * [new branch] new -> new ! [rejected] bad -> bad (non-fast-forward) ! [rejected] updated -> updated (fetch first)
One of the most useful features of Git (and that Mercurial doesn’t have), is remote name-spaces. So you can easily track “max/development”, “sarah/development”, etc. however, to properly track multiple Mercurial repositories, running shoes git-remote-hg needs to create a clone of the Mercurial repo, and if the repository is a big one, having multiple running shoes unrelated clones wastes a lot of space.
The solution is to use the Mercurial share extension running shoes , which is not really an extension, as it’s part of the core (but can only be used by activating the extension), so you can add as many Mercurial remotes as you want, and they would all share the same object store. Use SHA-1′s to identify revisions
Previously, Mercurial revisions were stored as revision numbers (e.g. the tenth commit is stored as 10), which means if history is rewritten there’s no way to tell that the revision running shoes changed, so the Git commit wouldn’t change either (as it’s cached).
Mercurial properly reports which is the current branch and bookmark, but only for local repositories. To get rid of the mismatch we always track “default” Don’t force bookmark updates
Unannotated tags don’t have an author in Git, but it’s needed for Mercurial, so instead of providing an empty author, use the one configured for Git. Fix replacing a file with a directory What’s next
This feature allows showing the Mercurial revision as Git notes: running shoes commit 6c88a31540012991de3add247a958fd83531256f Author: Felipe Contreras running shoes Date: Fri Aug 23 13:00:30 2013 -0500 Test Notes (hg): e392886b34c2498185eab4301fd0e30a888b5335
Enter your comment here... running shoes
Join 507 other followers
Powered by WordPress.com