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

Simpler import procedure

From: Michael Hübner <michael_at_mick-huebner.de>
Date: 2007-03-15 16:52:41 CET


the "import" procedure is IMHO not the simplest way to fill a repository
if you already have a lot of files. The problem is that you must
create a new directory tree which contains only the files which should
be versioned. (i.e. have to think about the roles of the files once).
When you imported this source tree, checked it out and build the system
and make your first commit you have to set the ignore filters (i.e. must
think about the roles of the files again).

To avoid this double work I usually

   1. create an empty repository,
   2. rename the original directory to "original"
   3. check the empty repository out into the wc directory
   4. copy/move the complete tree content (i.e. the source files and
      the generated files) (in the top directory and all subdirectories)
      from "original" into the wc directory
   5. make a commit
         1. set the ignore filters
   6. remove "original"

The technical problem is, that the ignore filters may only be set for
directories which are already in the repository. So the tree has to be
added level by level (top-down).

It would be nice to add the whole tree in one single commit-operation:
For this it must be possible to add ignore filters also for directories
which are not already in the repository but which are marked as "add to
the repository".

The fastest way to put an existing directory tree under the control of
subversion would look like this:

   1. operation "create a repository <name> in <base-url-path> and
      commit" executed in the wc directory

This means point 1.-6. were executed within one single operation.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 15 16:52:34 2007

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.