[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Bug in svnversion?

From: B. Smith-Mannschott <benpsm_at_gmail.com>
Date: 2006-12-29 20:34:07 CET

On Dec 29, 2006, at 17:56, Kevin Hung wrote:

> This seems like a bug in svnversion.
> I have the following directory and file structure.
> root -- d1 -- f1.txt
> root -- d2 - f2.txt
> d1 and d2 are directories. f1 and f2 are files.
> d2 is actually an external.
> If I make changes to f2.txt and run "svnversion ." at the root
> directory, I got a revision number without the letter M. I expect
> the letter M since I make changes to f2.txt.

This behavior doesn't surprise me in light of what the svnbook says
about disjoint working copies and svn:externals:


[...] The working copies created via the externals definition support
are still disconnected from the primary working copy (on whose
versioned directories the svn:externals property was actually set).
And Subversion still only truly operates on non-disjoint working
copies. So, for example, 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.

If this *is* intended behavior, perhaps a mention of this in the
svnbook's section on svnversion would be appropriate.

Out of curiosity, I looked up the documentation of
svn_wc_revision_status(...) but there's nothing there that pointed
out the bit about not crossing svn:externals boundaries. Presumably,
this is because it's a natural consequence of svn's design.

// ben

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 29 20:34:30 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.