update trickery

Attention Recent Updaters:

If you've updated your working copy with Revision 280 or later, you
probably didn't get the svn:ignore property change on your top-level
directory. In fact, you probably got a nasty 400 error. :-)

Thanks to Kevin Pilch-Bisson and myself, this should not happen with
the latest Subversion.

A (somewhat) easy fix is to make sure you've built Subversion with the
latest codebase, then `svn up -r 279` and back again with `svn up`.

The tricky part will be actually getting the latest codebase. You
might need to go into your working copy and do `svn up *` or something
similar (in order to avoid actually updating the top-level directory)
or just checkout a new working copy.

Acrobatically yours,
C-Mike

---------------------------------------------------------------------
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:36:45 2006