Johannes Schindelin schrieb: > Hi, > > I tried to refrain from commenting in this thread, because I do not want > to encourage people just to use msysGit and never even attempt to fix > their own issues. > > But I cannot let this go uncommented: > > On Mon, 28 Sep 2009, Felipe Contreras wrote: > >> IMO the key difference between hg and git is the storage model: hg >> stores deltas, while git stores snapshots. That would mean that certain >> operations are theoretically faster in git (e.g. checkout, diff) while >> others faster in hg, although with git's packed format I guess there's >> no operation faster in hg. This means that it doesn't matter how much >> hg's python code improves, or if they even re-write parts in C, they >> will never be able to match git's performance (unless they change the >> storage model, which essentially means changing the whole design -- >> won't happen). > > That is wrong. "git log -- <file>" will always be slightly faster in > Mercurial, for all the reasons you mentioned. > > In addition, Mercurial _has_ parts re-written in C for performance, which > renders it not-exactly more portable if you ask me. Last time I checked, > there was no way to compile a Python module with MinGW (or for that > matter, Python itself), but you needed MSVC... I have a shortish mercurial build script that works under Cygwin 1.5 and uses msys, py2exe and iscc to build an installable Mercurial package, but I'm not sure what this boils down to WRT C-versions of "modules". Maybe these are lumped into the resulting hg.exe, I never bothered to check the details. -- 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