Re: Importing from a working copy ... bad idea?

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.

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.

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.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail: Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow