begin quoting Lan Barnes as of Thu, Jun 08, 2006 at 06:56:04AM -0700:
[chop]
> Well said. (OK, really a buckboard with a lawnmower engine.)
Early tractors weren't far off from that. :)
> Also, thanks for (I guess?) defending my zeal.
I have to reconcile my opinion of your opinions somehow.
And I understand about being really pissed off about something. I
spend too much time there as it is.
> Really, the pain factor of switching to svn is like a couple of hours
> work for most home hobbyists. I *highly* recommend giving svn a try.
I'm not most, I guess. For times tried, four times failed. Dependency
hell is a major failing in my book... I don't have confidence that SVN
developers don't value cleverness too highly, either. Plus the docs
were condescending and offensive ("When did you last look at a ,v file?")
and the online community is typically rude and engages in the sort of
behavior I'd rather not be associated with.
As I hear about major improvements and get some time for it, I suppose
I'll go back and give it another try.
> Or Perforce, if free-as-in-beer doesn't cause a skin rash in you.
I'm going to set up a perforce server at home one of these days... I
can't say I like the "managed" aspect very much, and I tend to screw
up on the client side by having the wrong workspace set, which pushes
me towards the GUI clients. :(
But it has some neat features too. And it has shown me that file
renaming just isn't that important in real life. Doesn't matter
if the feature is there if you have developers that don't bother
to use it (as I had); and if you have to train 'em to use it all
the time, you can train 'em to the workarounds as well.
What we *need* -- I don't know if this has been done -- is a VC
system that can tell when a file has been "moved", and when one
has been derived from another, without specifically being told
this.
--
_ |\_
\|
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
