[BOOK] suggestion re 'in-place import'

I would *strongly* encourage the powers that be to consider including the
subversion FAQ entry "How can I do an in-place 'import' (i.e. add a tree
to subversion without moving or deleting the original working copy)?" in
the subversion book (perhaps as a "Tip" box, somewhere in Chapter 3 where
the process of importing is first introduced.)

Every project I have in subversion so far was already started when it
came time to import it so to get each under version control I resorted
to importing the base directory, moving the entire thing somewhere else,
checking the freshly imported thing out to where it had just been and
then one of the copies is removed or consigned to a sanity check tarball
backup. One of these projects was half a gig, so the import, move,
check out technique to put the project into a new svn repo was sort of
kludgey. Had I only known! I imagine many people start out going about
things in the way I did.

On the bright side, I am really glad that I managed to eventually find
out how to do this "idiomatically" rather than having to bother the user
list about it. So I applaud you all for having addressed it already,
though I think it is an apt side bar for the book. The use case to which
it applies seems quite prevalent. The book appears to approach things
(whether intentionally or not) in a "new repo" == "new project" kind
of way, whereas I find (at least in my world) that there are many times
where I will start fiddling with something and then after a week or so
I'll decide that it merits being put under version control. I suspected all
along that I might be operating according to an incorrect model.

So glad my old way is not the way to do this in any case...

marcel

-- 
Marcel Molina Jr. <marcel@vernix.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org