begin  quoting Lan Barnes as of Fri, Aug 17, 2007 at 07:29:16AM -0700:
> 
[snip]
> If you followed it, disgust for the CVS core team was long standing and
> fully justified. They treated every suggestion for a feature upgrade with
> a contemptuous dismissal: "that's the way CVS works and it's just fine."
> 
> The Subversion team was writing in direct opposition to this attute.
> Unfortunately, once they released svn, they adopted the same attitude for
> themselves. They rely on their (excellent) copy algorithm for everything
> -- branching, tagging -- and it's just not the same. They belittle every
> suggestion to add these features.

Meet the new boss, same as the old boss.

:(

I had high hopes for SVN. When they went with the database-and-WebDAV
architecture, those hopes were pretty much dashed. When they decided
that a huge dependency chain was "okay", those hopes were irredeemably
crushed.

Perforce seems to favor their merge feature in much the same way. Make
a branch? Integrate into an empty directory. Meh.

[snip]
> More complete commercial tools like Dimensions and Clearcase have process
> built in, and that's great if it happens to coincide with _your_
> processes, but plain hell if they don't.

I used Clearcase for nearly a year. Not, I'm told, like it was intended,
with a shared VOB and integration to the bug-reporting system, but more
like Perforce -- a checkout/checkin model with specially created views.

The one nice thing about Clearcase was the graphical history view and
the ability to checkout/checkin/branch/merge from the view.  It made the
GUI very useful. Too bad it was a file-only view.

Another nice-ish thing was that you could manually make relationships
between nodes.  If you hand-merged (e.g., cut-and-paste) a change from
one branch to another, you could record that without actually having
to use the tool to perform a merge. I never used it, but I think it
would be useful.

-- 
Anything is better than Visual SourceSafe.
Stewart Stremler


-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to