Karl Fogel <kfogel@newton.ch.collab.net> writes:
> Vladimir Prus <ghost@cs.msu.su> writes:
> > I'm confused about 'svn revert':
> >
> > bash-2.05a$ svn st
> > M ./Jamfile
> >
> > bash-2.05a$ svn revert
> > (Nothing reverted)
> >
> > bash-2.05a$ svn revert .
> > (Nothing reverted)
> >
> > It looks like in order to revert all the files in the current directory, I
> > should either list them all, or give '--recursive' option. Is this behaviour
> > intentional, and if so, what is the rationale?
>
> Yes, it's one of the few commands that's not recursive by default,
> intentionally. There could be a better usage hint in place of the
> silence when nothing gets reverted, though; care to patch?
No, silence is fine. I think what I'll do is just force revert to
take a target on the command-line, and `.' will no longer be the
default.
bash-2.05a$ svn revert
revert: Restore pristine working copy file (undo all local edits)
usage: revert TARGET1 [TARGET2 [TARGET3 ... ]]
Note: this routine does not require network access, and will
remove any .rej produced when a file is in a state of conflict.
Valid options:
--recursive: descend recursively
bash-2.05a$ svn revert .
bash-2.05a$ svn revert Jamfile
Reverted "Jamfile".
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:01 2006