Previous revision before move at new location

[Patrick Kulle]

Dear list,

I'm currently investigating on switching from CVS to SVN for our
projects in the office. Now I stumbled over a problem that I wasn't
able to solve by checking the book, FAQ, colleagues or Google. Maybe
you can help.

Assume the following scenario.

- There is a certain history on all objects (r1 to r199)
- At some point of time (r200) a directory is renamed in the
  repository ("svn move ^/trunk/foo ^/trunk/bar")
- The development goes on (r201 to ...)
- Someone wants to use trunk/bar/somefile.c with the code from r100 at
  the current location.

a) If the moving in r200 would not have happened 'someone' could
   simply go back locally by "svn up -r100 somefile.c". But in the
   above scenario this would just remove the file.

b) What he could do is "svn merge -r HEAD:100 somefile.c". But in this
   case there is no easy way of tracking/seeing which revision is 'in'
   somefile.c now. It is just locally modified.

Is there some way to get a behavior like in a) just in the new
location?

Thanks in advance,
Patrick
--
DSL-Preisknaller: DSL Komplettpakete von GMX schon für
16,99 Euro mtl.!* Hier klicken: http://portal.gmx.net/de/go/dsl02

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2414463

To unsubscribe from this discussion, e-mail: [users-unsubscribe@...].

[Giulio Troccoli-2]

>


Linedata Services (UK) Ltd
Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB
Registered in England and Wales No 3027851    VAT Reg No 778499447

-----Original Message-----

> From: Patrick Kulle [mailto:pkulle@...]
> Sent: 04 November 2009 17:06
> To: users@...
> Subject: Previous revision before move at new location
>
> Dear list,
>
> I'm currently investigating on switching from CVS to SVN for
> our projects in the office. Now I stumbled over a problem
> that I wasn't able to solve by checking the book, FAQ,
> colleagues or Google. Maybe you can help.
>
> Assume the following scenario.
>
> - There is a certain history on all objects (r1 to r199)
> - At some point of time (r200) a directory is renamed in the
>   repository ("svn move ^/trunk/foo ^/trunk/bar")
> - The development goes on (r201 to ...)
> - Someone wants to use trunk/bar/somefile.c with the code from r100 at
>   the current location.
>
> a) If the moving in r200 would not have happened 'someone' could
>    simply go back locally by "svn up -r100 somefile.c". But in the
>    above scenario this would just remove the file.
>
> b) What he could do is "svn merge -r HEAD:100 somefile.c". But in this
>    case there is no easy way of tracking/seeing which revision is 'in'
>    somefile.c now. It is just locally modified.
>
> Is there some way to get a behavior like in a) just in the
> new location?
>

I believe you want to use peg revision. Something like the following should work in your case

svn export <URL to repo>/trunk/foo/somefile.c@100

Check the book for a full explanation on peg revisions.

Giulio

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2414641

To unsubscribe from this discussion, e-mail: [users-unsubscribe@...].