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

Re: Best Practices question

From: Jeff Stuart <jstuart_at_computer-city.net>
Date: 2002-10-09 18:05:40 CEST

True, you do lose your history that way. Not sure if you could do the
following to keep it:

svn co /Microsoft/windows
cd windows
svn mkdir dos
cd ..
svn co /Microsoft/dos
cd dos
cp -R * ../windows/dos
cd ../windows/dos
svn add *
svn ci

Well that might not also keep the history... What you CAN do though is
put a log message that says "Refer to /Microsoft/dos repository for
older history" or something similar.

On Wed, 2002-10-09 at 11:50, Rafael Garcia-Suarez wrote:
> Jeff Stuart <furball@weboverdrive.com> wrote:
> > Easy. :) Import one repository into the other.
>
> This way you'll lost the history of the imported project.
>
> It should be possible to produce a list of patches (by
> svn diff -rN:N+1) for the old repository, and commit them
> to the 2nd repository.
>
> Caveats : metadata, copies, renames -- I don't know how
> svn will handle this. Apparently svn diff doesn't give
> any hints about copies or renames.
>
> Another possibility : hack the output of svn dump. But
> perhaps that's total nonsense.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 9 18:06:19 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.