All right, before I get down to work on Issue 493 (i.e. [non]recursive stuff),
I wanted to check what the behaviour should be. Below is a list of commands,
and what there defaults should be (* indicates already supported):
add non-recursive switchable (becomes import??)
checkout recursive switchable
commit recursive switchable
delete recursive non-switchable (you can't remove a dir,
but not it's children)
import recursive switchable (?)
proplist non-recursive switchable (change output to display
name of node prop belongs to in
propget non-recursive switchable (as above)
propset non-recursive switchable (as above)
propdel non-recursive switchable (as above)
*status recursive switchable
*diff recursive switchable
update recursive switchable
cleanup recursive non-switchable (doesn't make sense to
clean just part of a wc).
revert currently non-recursive, switchable
The other issue is what behaviour does --non-recursive have. My idea was that
if the target is '.' then is works on all files/dirs in the present dir. If
the target is a non-'.' dir, then it will work exclusively on the dir.
e.g. svn plist lists props on all immediate children of the current dir,
whereas svn plist dir lists props only on dir. The only thing I don't like
about this is svn up -n dir. Most people would expect it to do all children
of the dir.
What do people think about this?
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
Received on Sat Oct 21 14:36:44 2006
- application/pgp-signature attachment: stored