[
https://issues.apache.org/jira/browse/SVN-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Zhakov updated SVN-3743:
-----------------------------
Description:
{{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.
was:
{noformat:nopanel=true}
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.
{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)
