Re: stupid question (after couple of months with subversion)

Ben Collins-Sussman <sussman@collab.net> writes:

> > > (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

> > 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?)

RedHat Linux 2.4.14, glibc 2.2.4.
Apache/2.0.31-dev (Unix) DAV/2 SVN/0.8.0 mod_ssl/3.0a0 OpenSSL/0.9.6b

Don't remember all but here is build history:

compiled static BerkeleyDB 4.
compiled apache2 with OpenSSL
compiled subversion with neon in his directory, and paths to
BerkeleyDB and apr.

I can try to build newer subversion apache module today and see ...

-- 
This signature intentionally left blank
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org