Single-DB: should "status -u" recurse into missing dir? (merge_tests 16 failure)

2010-08-27 Thread Julian Foad
In single-DB world, the WC generated in merge_tests.py 16, a directory 'A/B/F/Q' has been deleted from disk without informing Subversion, so its status is 'missing'. Look at the difference between these two "svn status" runs on it: $ svn st A/B/F -vu !22 jrandom A/B/F

Re: Single-DB: should "status -u" recurse into missing dir? (merge_tests 16 failure)

2010-08-27 Thread Stefan Küng
On 27.08.2010 17:32, Julian Foad wrote: In single-DB world, the WC generated in merge_tests.py 16, a directory 'A/B/F/Q' has been deleted from disk without informing Subversion, so its status is 'missing'. Look at the difference between these two "svn status" runs on it: $ svn st A/B/F -vu !

Re: Single-DB: should "status -u" recurse into missing dir? (merge_tests 16 failure)

2010-08-27 Thread Julian Foad
> On Aug 27, 2010 11:33 AM, "Julian Foad" wrote: > > In single-DB world, the WC generated in merge_tests.py 16, a directory > > 'A/B/F/Q' has been deleted from disk without informing Subversion, so > > its status is 'missing'. > > > > Look at the difference between these two "svn status" runs on i

Re: Single-DB: should "status -u" recurse into missing dir? (merge_tests 16 failure)

2010-08-27 Thread Julian Foad
I (Julian Foad) wrote: > > On Aug 27, 2010 11:33 AM, "Julian Foad" wrote: > > > In single-DB world, the WC generated in merge_tests.py 16, a directory > > > 'A/B/F/Q' has been deleted from disk without informing Subversion, so > > > its status is 'missing'. > > > > > > Look at the difference betwe

Re: Single-DB: should "status -u" recurse into missing dir? (merge_tests 16 failure)

2010-08-27 Thread Greg Stein
Recurse. Show all the info. On Aug 27, 2010 11:33 AM, "Julian Foad" wrote: > In single-DB world, the WC generated in merge_tests.py 16, a directory > 'A/B/F/Q' has been deleted from disk without informing Subversion, so > its status is 'missing'. > > Look at the difference between these two "svn