I'm currently working with the svn folks on this one, but I thought
I'd let you know the situation.

At revision 5050, after I changed a couple things with merge.php, svn
mysteriously decided to also commit a whole bunch of other files I've
never touched. It looks like newline stuff was involved, because an
svn diff -r 5050 of
campsite/implementation/management/javascript/fValidate/readme.txt
(one of the files involved) lists basically only a newline as new.
These extra files I've never touched, so I halfway suspect that, given
my internet was a bit funky yesterday, there must've been some weird
disconnect going on that caused the mixup. And between revision 5049
and 5050 (15 minutes) is when this whole thing happened, so nothing on
my filesystem would've changed... very mysterious.

Now, how these files slipped into my svn commit is still a mystery to
me, but the real mystery is how to revert back to 5050. The normal
procedure is:

svn update -r 5050
svn -u status
svn diff
svn commit

( I also tried: svn update -r 5050, copying the files out, and then
with a fresh trunk copying them back over and svn -u status and svn
diff and svn commit--didn't work. The files involved are both binary
and txt files. )

With a local version of 1.2.3 of svn, svn update works, but svn -u
status / diff / commit do not work. I upgraded to 1.3.2 and svn -u
status worked, but not diff and commit.

I've been working with the svn folks on this, and we might have to
upgrade the svn server to the latest, although they aren't positive if
this bug has been reported.

Anyway, I thought I'd send this notice out as I'm in the middle of
working on a fix--perhaps another set of eyes will reveal something.
I'm pretty stumped.

Peter
--
Hartman's Brain Consulting | Openflows Networks Ltd. | Campware.org

gpg 1024D/ED6EF59B (7D1A 522F D08E 30F6 FA42 B269 B860 352B ED6E F59B)
gpg --keyserver pgp.mit.edu --recv-keys ED6EF59B