Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
To: dev@subversion.apache.org
From: Marc Strapetz <marc.strapetz@syntevo.com>
Subject: svn status API and missing switched flag
Message-ID: <561B75B5.2070204@syntevo.com>
Date: Mon, 12 Oct 2015 10:56:21 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Consider following working copy for which directory "dir" is switched:

$ svn status -v
                814      813 marc         .
     S          814      813 marc         dir
                814      356 strapetz     dir\sub.txt

Now, when invoking "svn status" in sub-directory "dir", the "switched" 
state is not displayed anymore:

$ svn status -v
                814      813 marc         .
                814      356 strapetz     sub.txt

 From command line, this may be reasonable, because the user may expect 
to see the status "relative" to his current working directory.

 From API perspective, the missing "switched" flag is not expected. I 
guess that usually a non-root and non-infinity "svn status" will be 
invoked to efficiently update the state of a certain directory (at least 
we do so). Still the state is usually expected to be relative to the 
working copy root.

To resolve this, I'd propose to change core "svn status" itself to 
evaluate the "switched" flag for the status root directory. This will 
result in an additional "S", but won't do any harm:

$ svn status -v
    S            814 813 marc .
                 814 356 strapetz sub.txt