Hi Ryan, On Thu, Apr 18, 2019 at 01:30 PM PDT, Ryan Schmidt wrote: > > 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?
You make a good point. Maybe I'm just more comfortable in the linux world and not as well versed with SVN. > > 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. I "thought" (perhaps incorrectly) that if I copied a file out of an existing ws dir and into a new non-ws directory; then later did an 'svnmucc put' of that file that SVN may treat the file as a new addition to the repo--since the file had never been checked into that particular location before. Is that not the case? Best regards, -- Mun
