Hi I'm not sure what you are trying to achieve.. but..
On Thu, Aug 19, 2010 at 1:25 PM, David Aldrich <david.aldr...@eu.nec.com>wrote: > Hi > > It has been suggested that I use peg revisions to solve this problem. > However, I don't understand peg revision syntax. > > As a test, I created a new text file in the trunk called pegtest.txt and > then made changes to it: > > r1855 commit pegtest.txt ver.1 > r1856 commit pegtest.txt ver.2 > r1857 commit pegtest.txt ver.3 > r1858 create tag of trunk > r1859 commit pegtest.txt ver.4 > ... > r1861 create branch of tag > r1862 commit pegtest.txt ver.5 > > > Now if I look at my branch, pegtest.txt is ver.3 i.e. r1857 as expected. > > If, in my branch, I do: > svn update -r1856 pegtest.txt > I'm still on old subversion not having caret-functionality so I would do (in the branch): svn merge http://host/trunk -c -1859 . svn ci -m"reverted [1859] from branch" > pegtest.txt gets deleted. I guess this is because the branch did not exist > in r1856. > > How can I use a PEG revision to bring pegtest.txt r1856 from the trunk into > the branch please? > > BR > > David > >
