Matt Mackall wrote: > On Thu, Feb 01, 2007 at 12:58:42AM +0100, Jakub Narebski wrote: >> Sidenote 1: it looks like git is optimized for speed of merge and checkout >> (branch switching, or going to given point in history for bisect), and >> probably accidentally for multi-branch repos, while Mercurial is optimized >> for speed of commit and patch. > > I think all of these things are comparable. Hierarchical tree objects in git optimize for speed of merge and checkout IMVHO, as you need only to check out one hash to know if you have to descend into subdirectory, or if given subdirectory haven't changed. Flat manifest file in Mercurial (and also "filename buckets") makes commits faster, I think. >> Sidenote 2: Mercurial repository structure might make it use "file-ids" >> (perhaps implicitely), with all the disadvantages (different renames >> on different branches) of those. > > Nope. How it is so, if the blobs (file contents) are stored filename hashed? IIRC hg has some scheme to deal with renames, but it is file-id (file identity) based AFAIK. -- Jakub Narebski Poland - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html