On Tue, Jul 26, 2011 at 06:42:39PM +0200, Andreas Krey wrote: > On Tue, 26 Jul 2011 10:09:47 +0000, Les Mikesell wrote: > ... > > Yes, but it is then a mixed rev and needs an update. That is, the > > changes you committed belong to the rev the commit creates while the > > unchanged files belong to the rev of the prior update or checkout. > > This is one of the high strangitude svn behaviour artefacts: That you > can't do two consecutive commits without getting an error (in some > relatively popular cases).
There were some annoying bugs in this regard which have been fixed partly in 1.6.16 and completely 1.7: http://subversion.tigris.org/issues/show_bug.cgi?id=3525 http://subversion.tigris.org/issues/show_bug.cgi?id=3526 (<-- this one in particular was annoying) http://subversion.tigris.org/issues/show_bug.cgi?id=3533