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

Merging - why do I need a path ?

From: Shakespeare, Simon \(Pensions\) <Simon.Shakespeare_at_capita.co.uk>
Date: 2005-11-01 12:07:47 CET

Hi - Can anybody explain to why when doing a merge you need to enter the path in the following manner:

svn merge --dry-run -r 40:41 svn://ipofserver/phoenix/trunk/gui/mpa c:/scstest/hiptapp/mpa

I'm trying to merge the commit that resulted in revision 41 - surely subversion knows what path(s) in the repository that revision 41 related to so why can't I just enter svn://ipofserver - I can sort of undertand why I need to enter a destination path for my working copy but am a confused what happens if revision 41 included several files in different directories - do you just use the top most path as the path for your working copy.

The reason I wanted to do this was to try & simplify my merging. When I do a commit I store that revision against a ticket number in a database & assumed that it would have been sufficient just to store the revision number rather than all the paths.

Thanks - Can you include me in the reply as I not a member of the users mailing group - well I was but I got swamped with emails & my boss wasn't happy !


This email and any files transmitted with it are confidential, and may be subject to legal privilege, and are intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error or think you may have done so, you may not peruse, use, disseminate, distribute or copy this message. Please notify the sender immediately and delete the original e-mail from your system.

Computer viruses can be transmitted by e-mail. Recipients should check this e-mail for the presence of viruses. The Capita Group and its subsidiaries accept no liability for any damage caused by any virus transmitted by this e-mail.
Received on Tue Nov 1 12:29:11 2005

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.