On Sat, Jun 7, 2014 at 4:08 PM, <to...@acm.org> wrote: > > I completely agree with the points other than the one that "the DVCS > is the only tool that can effectively manage the EOL convention of the > files". I use a text editor daily that is capable of normalizing EOL > convention (though of course there are few things capable of starting a > flame war as effectively as suggesting to any random group of people that > their OS or text editor is inadequate to some task). :) > > I didn’t say that (“..only tool..”). But, using tools is all about > convenience. Yes, we can use Python, Lua, or whatever other scripts to do > whatever work isn’t done automatically. But, this loses on convenience. I > could also keep (as I did until I started using FOSSIL) all my older > versions in dated RAR files, and go back to any version I want to. But, at > what cost in terms of convenience? >
Fair enough. I like fossil because of the convenience of having the wiki & ticket systems integrated into the single file repository. I dislike git because of the inconvenience of needing to earn a post graduate degree to understand it. ;) Again, it doesn't seem overly inconvenient to add a little scripting, but agree that it is "less convenient". > > But I can also see the point to the idea that "this is the file I > created and this is exactly what I want to see when I pull it out of a repo > that I put it into". > > And that’s why those things should always be optional. I never said it > should be imposed on everyone just because some like it this way. But not > having the option is akin to the other side imposing their ‘right’ way on > everybody else. > Flexibility is a nice thing, I agree. I suspect that's why the CRNL glob was put in, to give flexibility to people who didn't want to see warnings because their platform didn't conform to the unixen EOL standard. Or that so much effort is spent to make fossil portable between Windows and posix platforms, or why there is a built in web based GUI interface where other tools would tell you to just use the command line & terminal mode. There are ideological differences between git and fossil. It's why Linus created git as he felt the existing tools were inadequate for various reasons (be they centralized in the case of svn or pricey in the case of bitkeeper). It's why DRH created fossil, who wanted immutable history vs rewritten history, among other things. All software is going to tell you there is a right way to do certain things. git vs fossil, vi vs emacs, Windows vs unixen, c++ compilers vs python interpreters. In any case, my offer still stands to help script a solution that'll give you what you need! I'm by no means a fossil expert, but I'm confident I could help with something like this if you needed it. SDR
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
