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

Re: "svn co -d" and updates

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2001-11-30 16:41:41 CET

On Fri, Nov 30, 2001 at 09:36:07AM -0600, Shaw Terwilliger wrote:
> Let me first say that I really like the notion of Subversion soon replacing
> CVS in most or all of its installations. I think the internal design is
> simple and neat, and the team has done a good job focussing on the features
> important to developers.
>
> I've been building the svn trees for the last few weeks, and I'm trying to
> determine whether the behavior I'm seeing is intended (and I just haven't
> found the documentation to let me know).
>
> I check out any tree with the -d option, and supply a name other than
> the repository's last component, and svn gets confused when I later do things
> like "svn update" inside that tree. The client can't seem to map its
> not-quite-maching-the-repository working copy directory name with the file
> info inside it.
>
Could you give some more details. I always check out the subversion
source tree like this:

svn co http://svn.collab.net/repos/svn/trunk -d svn.static (or svn.shared,
or whatever)

and I have never noticed any problems.
>
> --
> Shaw Terwilliger <sterwill@sourcegear.com>
> SourceGear Corporation
> 217.356.0105 x 641

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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:50 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.