[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: update trickery

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2001-10-23 18:00:17 CEST

On Tue, Oct 23, 2001 at 10:01:41AM -0500, cmpilato@collab.net wrote:
> 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`.
To reduce the amount of compiling you have to do, you might try
svn up -r 279 --non-recursive.

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

Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall

  • application/pgp-signature attachment: stored
Received on Sat Oct 21 14:36:45 2006

This is an archived mail posted to the Subversion Dev mailing list.