subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mun Johl <>
Subject Re: Importing from a working copy ... bad idea?
Date Thu, 18 Apr 2019 19:04:58 GMT
Hi Thorsten,

On Thu, Apr 18, 2019 at 11:29 AM PDT, Thorsten Schöning wrote:
> Guten Tag Mun Johl,
> am Donnerstag, 18. April 2019 um 18:10 schrieben Sie:
> > Hmm, I was not aware of svnmucc.  But after reading about svnmucc I
> > think what I would need to do is create the directory structure I want
> > outside of a valid workspace; and then write a script that would use
> > 'svnmucc mkdir' and 'svnmucc put' to populate the ^/trunk/new_project
> > directory.
> How is writing a script for using svnmucc any easier than doing svn
> copy on some working copy? The latter should be easier because you
> don't need to take care about accidently committing intermediate
> changes.

I was thinking I would do all of the manipulation via linux commands and
get the structure the way I wanted; and then write a script that
basically only did the svnmucc mkdir and put commands.  To me, that
seemed easier than writing a script for all the various svn copy's that
would be required.

However, upon further reflection: Since many files will be renamed
and/or moved to different relative locations, the svn log for those
files would not be maintained anyway (I don't think) by svnmucc.
Therefore, using svnmucc may not be the answer I was looking for
after all.

> And why do you need a script at all compared to simply using some
> SVN-GUI-client allowing you to use Drag&Drop and stuff? Clients like
> TortoiseSVN are very good in building new dir structures from existing
> working copies, because they allow you to D&D individual files,
> directories, multiple files of some dirs etc. easily.

We don't currently have an SVN-GUI-client.

> Depending on the complexity and size of your repo, you don't even need
> to checkout everything, just set "depth" in your GUI-client of choice
> as needed.

As it turns out, I may simply use 'svn import' and forget about trying
to preserve the existing svn logs.  It doesn't seem to be worth the ROI
at this point.

Thanks for your comments.



View raw message