cmpilato@collab.net writes:
> Miroslav Zubcic <mvz@crol.net> writes:
>
> > OK here is a little example:
> >
> > (mvz){crolvax}[proba-01]$ svn st
> > (mvz){crolvax}[proba-01]$ vi foo.c # editing existing file ...
> > (mvz){crolvax}[proba-01]$ echo "blablabla" > file001
> > (mvz){crolvax}[proba-01]$ svn st
> > ? ./file001
> > M ./foo.c
> > (mvz){crolvax}[proba-01]$ svn add file001
> > (mvz){crolvax}[proba-01]$ svn ci
> > Adding /home/mvz/proba-01/file001
> > Sending /home/mvz/proba-01/foo.c
> > Committed revision 29.
> > (mvz){crolvax}[proba-01]$ svn st
> > A ./file001
> > M ./foo.c
> > (mvz){crolvax}[proba-01]$ svn revert file001 mangle.c
> > Reverted file001
> > Reverted mangle.c
>
> Whoa. That's ... uh ... broken, dontcha think? I wonder what could
> be happening here...
That is *way* broken. After a commit, you shouldn't be seeing those
'A' and 'M' codes anymore. They should have each been bumped to
working revision 29!
Miroslav, what platform are you running on? Give us the history of
your subversion build. (Can anyone else reproduce this?)
---------------------------------------------------------------------
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:10 2006