Re: [Tcllib-devel] Regarding SourceForge, the Tcllib CVS, and transitioning somewhere.

[Jeff H. <je...@Ac...>]

On 2011-02-15, at 6:27 PM, Kevin Kenny wrote:
> On 02/15/2011 01:04 PM, Andreas Kupries wrote:
>> Regarding the core assumption behind the argument, of git not being good on
>> Win, that I can't really evaluate. I haven't used git very much and not at all
>> on Windows.
> 
> Git sort of works on Windows, but you have to install a ton of other
> stuff first, and I'd practically have to virtualize to do it (cygwin
> conflicts and the like). Fossil is a single executable on Windows and
> works just as well there as it does on Unix. My only annoyance is that
> it cannot be configured to do line-ending substitution. One of these
> days I'll do some scripts to work around it; I understand drh's
> reluctance to have the capability in the fossil mainline, given
> that the committed version of a file must be bit-for-bit identical
> to what the developer presented.

That is false logic, and is why all other revision control systems have the option to tag a file as text or binary.  To the developer, it's not bit-for-bit a file, it is a TEXT file with set contents.  You should be able to diff, push and pull those across different OSes and see exactness (or lack thereof) in a TEXT context.

Jeff