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

Re: strange behavior in svn co

From: Joseph Dunn <jdunn14_at_gmail.com>
Date: 2006-07-26 15:59:17 CEST

Sorry for the noise, this wasn't clear to me from the documentation I
skimmed. Thanks for the pointer. One thing though, it seems to me
that more intuitive behavior (preventing people like me from needlessly
complaining) would be that if a peg revision was specified where there
was no object at that path svn would take the object from the most
recent previous revision where something did exist at that path. Oh
well, I realize this is probably not especially efficient, just my 2


On Wed, 26 Jul 2006 09:51:13 -0400
"Gale, David" <David.Gale@Hypertherm.com> wrote:

> Joseph Dunn wrote:
> > I recently tried to check out an old version of a directory from my
> > repository and found that I couldn't. Months ago I deleted this
> > directory using svn del, so I looked up which revision it was still
> > around in and then attempted to do an svn co --revision=X. Instead of
> > checking out the directory it complains about not being able to find
> > it in the head revision.
> >
> > Interestingly, I can create an empty directory in the repository at
> > the same path, check out the now empty directory, then "update" back
> > to the revision I want. Thinking this is a bug.
> >
> > I've attached a bash script that reproduces the simplest case I could
> > come up with. Check it for exact details.
> >
> > -Joseph Dunn
> Check out peg revisions in the book. What you want to do is "svn co
> <folder>@X".
> -David

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 26 16:06:45 2006

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

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