Hello,
I'm new to Subversion, and new to this list, so please forgive any gross
RTFM's.
(Before uttering nary a complaint, let me start by congratulating and
thanking the Subversion team and developer community for having provided
such an excellent and flexible tool! You have created an awesome
upgrade path to CVS users, and I am deeply grateful for all your hard
work.)
This morning I noticed a discrepancy between the way file contents and
directory properties are committed across svn:externals projects, and
wanted to make sure that the behavior was known (and hopefully made
consistent in some later version).
Although the Fogel book states that:
"if you want to commit changes that you've made in one
or more of those external working copies, you must run
svn commit explicitly on those working copies --
committing on the primary working copy will not recurse
into any external ones"
Presumably this is no longer true, since I've been happily running 'svn
commit' from the top level of my "amalgamated" project, and seeing that
commits do indeed carry down into externals.
However, I noticed that when setting directory properties (via a 'find
-type d | xargs svn propset ...' kludge, since I guess 'propset -R'
isn't ready yet), I did still have to change into each external
directory mount and manually commit those changes (even though a
top-level "svn status" was able to see and report that the properties
were modified).
Thank you,
Mark Zieg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 16 18:02:12 2005