Re: How to move folder from one path to another along with all revisions

Thanks all for your reply i'll try with svn mv command and get back to you if face any issue. Mohsin -- View this message in context: http://subversion.1072662.n5.nabble.com/How-to-move-folder-from-one-path-to-another-along-with-all-revisions-tp192143p192157.html Sent from the Subversion User

Re: How to move folder from one path to another along with all revisions

On Fri, Feb 20, 2015 at 9:01 AM, Mohsin wrote: > Hi, > > Suppose I have one folder in Repo1 (http://abc.com/SVN/Repo1/folder1) and I > have moved that folder to some new path which is (http://abc.com/SVN/Repo1). > Point is I want to move that folder along with all its revisions to new path > when

Re: How to Switch, or Update, a file that exists only in a branch ?

On Fri, Feb 20, 2015 at 9:26 AM, Kerry, Richard wrote: > > > Also, to follow up points in Les' response: >> If you put your documents in directories and branch the directory instead >> of doing individual file operations, you'll have a place to switch to when >> you want to access the contents of

AW: How to move folder from one path to another along with all revisions

When using the Tortoise SVN client i would open RepoBrowser and move it in the repo. I am not sure if that will preserve history but it's the most powerful thing I am aware of. -Alex.

Re: How to move folder from one path to another along with all revisions

If it makes you feel better, you can use "svn rename" instead. > On Feb 20, 2015, at 8:39 AM, Mohsin wrote: > > Thanks but my second question was how do i move folder to new path with all > its revision history ? Is it possible or we can't do this ? Actually moving > folder to new path is easy

Re: How to move folder from one path to another along with all revisions

This is the whole purpose of the svn mv-command. The history is kept if you use that command. Or am I getting your question wrong? Regards, Stefan Thanks but my second question was how do i move folder to new path with all its revision history ? Is it possible or we can't do this ? Actually mov

Aw: Re: How to move folder from one path to another along with all revisions

> Thanks but my second question was how do i move folder to new path with all > its revision history ? Is it possible or we can't do this ? Actually moving > folder to new path is easy but question is moving folder with all its > history revisions to new path too. svn mv/cp *retains* *all* *histor

Re: Require Information regarding Visual SVN Server

I'm so sorry, the email went to users@ Subversion mailing list unintentionally. Please disregard. On Fri, Feb 20, 2015 at 6:32 PM, VisualSVN Team wrote: > Hello, > Thank you for the reply. > >> Logical Separation on Entities are required for us to maintain the Multi >> domain infrastructure. Ple

Re: How to move folder from one path to another along with all revisions

Thanks but my second question was how do i move folder to new path with all its revision history ? Is it possible or we can't do this ? Actually moving folder to new path is easy but question is moving folder with all its history revisions to new path too. Mohsin -- View this message in contex

Re: Require Information regarding Visual SVN Server

Hello, Thank you for the reply. > Logical Separation on Entities are required for us to maintain the Multi > domain infrastructure. Please find the attached snapshot. Here we have > configured SVN server under forest root and were able to map the access > rights to the users from various sub do

RE: How to Switch, or Update, a file that exists only in a branch ?

I don’t feel I've had a satisfactory answer to my original question yet. Full details below, including mode details/use cases, but in short : > I have a couple of files that exist only in a branch which I’d like to have > within my Working > Copy. If the files exist in the Head I can use “switch

Re: svnsync problems

> On Feb 20, 2015, at 8:21, Branko Čibej wrote: > >> On 20.02.2015 13:59, Nico Kadel-Garcia wrote: >> On Fri, Feb 20, 2015 at 5:50 AM, Philip Martin >> wrote: >>> "Andreas Stieger" writes: >>> In addition to what Philip wrote, for initializing a sync to a target created via hotcopy

Re: How to move folder from one path to another along with all revisions

http://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.move.html Hi, Suppose I have one folder in Repo1 (http://abc.com/SVN/Repo1/folder1) and I have moved that folder to some new path which is (http://abc.com/SVN/Repo1). Point is I want to move that folder along with all its revisions to new path whe

How to move folder from one path to another along with all revisions

Hi, Suppose I have one folder in Repo1 (http://abc.com/SVN/Repo1/folder1) and I have moved that folder to some new path which is (http://abc.com/SVN/Repo1). Point is I want to move that folder along with all its revisions to new path when i check history of that folder there should be all revision

Re: svnsync problems

On 20.02.2015 13:59, Nico Kadel-Garcia wrote: > On Fri, Feb 20, 2015 at 5:50 AM, Philip Martin > wrote: >> "Andreas Stieger" writes: >> >>> In addition to what Philip wrote, for initializing a sync to a target >>> created via hotcopy, you will find "svnsync init --allow-non-empty" >>> very useful

AW: Making an (external) working copy readonly

> > Is there a way to make such svn:externals read-only? > > The easiest is to tie it to a specific tag. That requires write access for > *someone* who runs the third party repo to set up tags. Make a "lock" of the files on the server mandatory for check in. By this people will need to grab the l

Re: svnsync problems

On Fri, Feb 20, 2015 at 5:50 AM, Philip Martin wrote: > "Andreas Stieger" writes: > >> In addition to what Philip wrote, for initializing a sync to a target >> created via hotcopy, you will find "svnsync init --allow-non-empty" >> very useful. > > But only after upgrading as that is not present i

Re: Making an (external) working copy readonly

On Fri, Feb 20, 2015 at 7:05 AM, Niemann, Hartmut wrote: > Hello! > > > > I would like to prevent accidental commits into subdirectories that are > svn:external in our development projects. > > > > If I understand the documentation correctly, a svn:external is a complete > and independent working

Making an (external) working copy readonly

Hello! I would like to prevent accidental commits into subdirectories that are svn:external in our development projects. If I understand the documentation correctly, a svn:external is a complete and independent working copy on its own. Is there a way to make such svn:externals read-only? If no

Re: svnsync problems

"Andreas Stieger" writes: > In addition to what Philip wrote, for initializing a sync to a target > created via hotcopy, you will find "svnsync init --allow-non-empty" > very useful. But only after upgrading as that is not present in 1.6. -- Philip Martin | Subversion Committer WANdisco // *No

Re: svnsync problems

> Tony Sweeney writes: > > running under Apache. I set the svn:sync-last-merged-rev revprop on > > r0 to reflect the newest revision on the hotcopy. In addition to what Philip wrote, for initializing a sync to a target created via hotcopy, you will find "svnsync init --allow-non-empty" very u

Re: svnsync problems

You are making things very hard for yourself by running 1.6.11, it is very old and no longer maintained, unless your distribution is backporting fixes. A newer version will have fewer bugs and better performance. 1.6 has a hotcopy bug http://subversion.tigris.org/issues/show_bug.cgi?id=3596 t

Re: crash report

Hi Klaus, the SVN developers don't provide Windows binaries themselves. Without telling which distribution you are working with (aka: where you got the files located under C:/opt/subversion_1.7) the given dmp-file is merely useless as most likely is the given stacktrace. Regards, Stefan Fr

crash report

Freundliche Gr??e / kind regards i. A. Dipl.-Phys. Klaus Rezepka Entwicklung Powertrain [cid:luw_logo6a3f87] Lauer & Weiss GmbH Kompetenzzentrum f?r Modulentwicklung H?henstra?e 21 70736 Fellbach Tel: +49 711 520889 259 Fax: +49 711 520889 20 Mail: klaus.reze...@lauer-weiss.de

Re: svn: E155011 "out of date" error and svn: E160020 "already exists" error

Hi James, the error sounds to me as if the file you wanted to add was already commited. Did you try svn up before svn commit? Regards, Stefan I renamed a package (folder name) and then renamed two files under it (the renamed folder). Then I use kdesvn to do commit which will add and then c