[
https://issues.apache.org/jira/browse/SVN-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14929617#comment-14929617
]
Ivan Zhakov edited comment on SVN-3743 at 10/18/15 10:09 AM:
-------------------------------------------------------------
This has been the case since 1.0 and was deliberately designed this way. When
looking through the eyes of the outer working copy, the inner working copy is
not part of the working copy.
The new in 1.7 externals apis makes it much easier to obtain the difference
from code.
was (Author: rhuijben):
{noformat:nopanel=true}
This has been the case since 1.0 and was deliberately designed this way. When
looking through the eyes of the outer working copy, the inner working copy is
not part of the working copy.
The new in 1.7 externals apis makes it much easier to obtain the difference
from code.
{noformat}
> svn status reports nested working copies as "unversioned"
> ---------------------------------------------------------
>
> Key: SVN-3743
> URL: https://issues.apache.org/jira/browse/SVN-3743
> Project: Subversion
> Issue Type: Improvement
> Components: libsvn_wc
> Affects Versions: trunk
> Reporter: Stefan Sperling
> Fix For: unscheduled
>
>
> {{svn status}} currently reports working copies inside working copies as
> "unversioned". It would be nice if it made a distinction between unversioned
> content and content which is or could be managed by Subversion.
> A new kind of notification could be generated to indicate that a subdirectory
> is in fact a nested Subversion working copy.
> Note that nested working copies may be at an older or a newer working copy
> format, which complicates task this a bit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
