Ah -- I can get the same behavior, but only when I don't specify the
target of the second commit. Nice to know, in case it ever comes up
again, though it would probably be considered a bug by the CVS
maintainers at this point.
Anyway, this is getting farther from Subversion, so I'll not post more
on it.
-K
Greg Hudson <ghudson@MIT.EDU> writes:
> I expected Christian to be wrong as well, but I got a surprising result
> with CVS 1.10. (Dunno if the version difference is an issue.) I found
> that if I did a "cvs ci" with no arguments, I got an up-to-date check
> failure, but I could still do a "cvs ci bar", of course. Here is my
> command history:
>
> 1 14:26 setenv CVSROOT /tmp/repos
> 2 14:27 cvs init
> 3 14:27 mkdir $CVSROOT/dir
> 4 14:27 cd /tmp
> 5 14:27 cvs co dir
> 6 14:27 cd dir
> 7 14:27 touch foo bar
> 8 14:27 cvs add foo bar
> 9 14:27 cvs ci -m ''
> 10 14:27 cd ..
> 11 14:27 cvs co -d dir2 dir
> 12 14:27 cd dir
> 13 14:27 echo foo > foo
> 14 14:27 cd ../dir2
> 15 14:27 echo bar > bar
> 16 14:27 cd ../dir
> 17 14:27 cvs ci -m ''
> 18 14:28 cd ../dir2
> 19 14:28 cvs ci -m ''
> 20 14:28 cvs ci -m '' bar
> 21 14:29 cvs --version
>
> Command 19 yielded an error, while command 20 succeeded.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 6 20:49:38 2002