"Bert Huijben" <bert_at_qqmail.nl> writes:
>> From: Philip Martin [mailto:philip.martin_at_wandisco.com]
>> I'd like 'svn status' to start indicating when a working copy is
>> sparse, probably by using 'P' like svnversion. It could also be used
>> to indicate not-present nodes.
> Where would you like it to report that 'P'. On directories with depth <
> (Trying to think of a place where that makes sense)
Much the same way it reports 'S' for switched.
> $ svn status
> M subversion\libsvn_wc\update_editor.c
> M subversion\libsvn_wc\wc-queries.sql
> M subversion\libsvn_wc\wc_db.c
> M subversion\libsvn_wc\wc_db.h
> Would that indicate a change on a directory? (Otherwise sparse directories
> aren't even in the output of svn status)
I think it's a bug that sparse directories are not in the output. How
does one check whether a working copy is sparse or not? I can parse
the output of 'svn info --recursive' but that's not ideal.
> (Adding yet another column doesn't make things more understandable)
I think it would have to be a new column.
> Maybe in svn status -v?
> svn info already reports sparse directories, but it currently has no way to
> report excluded subdirectories and files. (Which I see as another kind of
> sparse directories). And if we think of adding excluded as sparse, something
> tells me that we should also look at absent.
> Just one thing: One of the major objectives of WC-NG is to make 'svn status'
> noticeable faster. Adding more calculations to that might work in the
> opposite direction.
I don't think retrieving one more column is going to be significant.
Received on 2010-03-14 15:29:38 CET