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

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

From: Ryan Schmidt <ryandesign_at_macports.org>
Date: Thu, 18 Apr 2019 15:30:47 -0500

On Apr 18, 2019, at 14:04, Mun Johl wrote:

> I was thinking I would do all of the manipulation via linux commands and
> get the structure the way I wanted

What I haven't understood in this thread is why you think that's easier than using the corresponding Subversion commands.

For example, if you were planning on using "mkdir", "cp" and "mv" to arrange your new project, why can't you use "svn mkdir", "svn cp" and "svn mv" instead, and then once you're happy with it "svn commit" it?

> 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.

Why wouldn't it preserve the history? Preserving history is the whole point.
Received on 2019-04-18 22:31:03 CEST

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.