Re: svn commit: r26495 - in trunk: subversion/libsvn_client subversion/tests/cmdline www/merge-tracking

Daniel Rall <dlr@finemaltcoding.com> writes:

> Yes, you'll always want 'svn cp -g'.

Sorry if I missed something, but I still think contacting the
repository should be the default, with a separate option to skip
the contact. There's the abstract argument that if an option is
nearly always required, you've chosen the wrong default. But we
have a more compelling argument.

Users have been running svn cp for years, without -g, naturally.
They hear 1.5 has merge tracking, but aren't going to read the
release notes in enough detail to note that they have to use cp
-g all the time. Even those who do are going to have trouble
adapting their habits. Then, later on, they'll find out that
merge tracking "isn't working". I think that's bad.

Subversion strives to be WAN-friendly, but does not strive to be
distributed, i.e. network-independent. We should optimize for
the common case. When someone runs svn cp WC WC on a plane,
they'll eventually get an error message about name lookup,
connection refused, or whatever, and a warning that we're copying
without mergeinfo.

--
Eric Gillespie <*> epg@pretzelnet.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 11 00:44:08 2007