From: Petr Baudis Date: Tue, 28 Jun 2005 15:07:52 GMT Subject: Re: Mercurial vs Updated git HOWTO for kernel hackers Message-ID: <20050628150752.GC1275@pasky.ji.cz> In-Reply-To: <42BC112C.1040009@qualitycode.com> Dear diary, on Fri, Jun 24, 2005 at 03:57:00PM CEST, I got a letter where Kevin Smith told me that... > - Can run on (native) MS Windows > (necessary for me because I often work on cross-platform projects) I'd expect everything to work fine with Cygwin (or with only minor problems easy to fix) or just any working bash + GNU coreutils installation. Any issue with that? > - Python code can be more clear and expressive (IMHO) > > In the long run, I think the python code base will be easier to maintain > and enhance. A rewrite of cogito in python or ruby would be cool. I've planned to rewrite Cogito in Perl, but it turned out the shell scripts really are far from the PITA they appeared to be - they work just fine and feel quite comfortable from the maintenance standpoint as well. It surprised me too but I don't plan to rewrite Cogito in a different language soon. > One advantage that cogito has is that git viewing/browsing tools can > operate directly on cogito repos. But a psychological drawback is the > ongoing confusion between git and cogito. Questions: Would a git-based > tool that writes to the repo (such as StGIT) mess up a cogito repo? Can > you switch a repo between git and cogito or back, at any time? Cogito's only unusual requirement (well, expectation) is that HEAD is a symlink to .git/refs/heads/master, and .git/refs/heads/master should reflect your current head. I will try to ease up this restriction so that things will mostly work even if you just have HEAD. I think that most auxiliary commands (e.g. cg-log - you just have to love it) should work on any sensible git tree (but I didn't test it - yet). -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ be careful, some twit might quote you out of context..