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

Branching with missing revisions

From: Kevin Ballard <kevin_at_sb.org>
Date: 2004-08-11 10:32:30 CEST

I just updated to Subversion v1.1.0 RC 2 and I tried creating a branch
in a project I was working on. I had updated my source to the latest
revision and made a few changes but one of the project admins decided
he didn't want that change in the trunk (at least, not yet), so I did
an `svn copy . <svn repo>/branches/resizable`. After that I did an `svn
switch <svn repo>/branches/resizable` and I saw a lot of changes
happening. After a bit of looking I discovered that the copy copied an
old revision over. The copy action was revision 209 and the trunk held
the correct stuff but the branch held the contents of revision 205 in
the trunk instead of the previously-up-to-date revision 208 (which my
WC was a modified form of). Doing an `svn merge -r 205:208 <svn
repo>/trunk` in my switched WC fixed it, but the question is how did
this happen in the first place? My WC was definitely up-to-date.

So can somebody explain this behaviour? Thanks.

Kevin Ballard

  • application/pkcs7-signature attachment: smime.p7s
Received on Wed Aug 11 10:33:15 2004

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.