Re[2]: [TSVN] [BUG] Problem with detection of changes in svn:externals included folders

Hello.

> Ok, the bug is fixed. I wonder when it happened that external folders
> don't have the svn_wc_status_external status anymore (did they have it
> ever? If not then this was broken from the beginning...).

> I think with this fix the other reported strange things should be gone
> too. So all who reported problems with externals when committing please
> try the next nightly build (>= revision 1941).

I've just tried r1948, and the problem with TSVN stopping scanning the
working copy seems gone: I can see all my changed files, even after
the 'changes in svn:externals won't be autocommitted' warning. Thanks
a lot, Stefan!

But I keep getting that warning... After carefully studying the
working copy, I think the problem is related to the following.

Some of svn:externals targets in my WC are not immediate children of a
versioned directory the prop was set on.

E.g. on '/libs' folder I have the following svn:externals prop set:
exports/mask_1 http://path/to/repo/folder

In the WC, the following directory structure gets created after 'svn
update':
|
|---/libs (versioned folder, with svn:externals set)
| |
| |---/exports (*UNVERSIONED* folder!)
| |
| |---/mask_1 (versioned folder, corresponds to the URL in svn:externals on /libs)

The /exports unversioned folder (intermediate) is the only thing that
could possibly trigger that warning in the commit dialog. There're no
modified or unversioned files in the /mask_1 dir.

> Stefan

--
Best regards,
 Dmitry Radzevich
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org