> -----Original Message-----
> From: Philip Martin [mailto:philip.martin_at_wandisco.com]
> Sent: zondag 14 maart 2010 14:38
> To: Greg Stein
> Cc: dev_at_subversion.apache.org
> Subject: Re: svn commit: r921445 - in /subversion/trunk/subversion:
> include/private/svn_wc_private.h include/svn_wc.h
> libsvn_client/commit.c libsvn_wc/entries.c
> Greg Stein <gstein_at_gmail.com> writes:
> > $ svn rm path/subdir
> > $ svn commit path/subdir
> > $ svnversion
> > Should it report "just r9", or should it report "r9-10" ?
> We could change the definition of r9P to include not-present as well
> as excluded.
> 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)
$ svn status
Would that indicate a change on a directory? (Otherwise sparse directories
aren't even in the output of svn status)
(Adding yet another column doesn't make things more understandable)
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
Received on 2010-03-14 15:18:48 CET