Re: Takeover Take 2 Was: Re: the 'takeover' feature

Michael Sweet wrote:
> Molle Bestefich wrote:
> > Therefore I'd like to see a new subcommand, which would convert local
> > files into a working copy. That's exactly the same functionality that
> > Alan proposes: checkout BASE files and create .svn folders, but change
> > nothing else. Just for laughs, let's call this 'svn integrate'.
> > ...
>
> That sounds more like an option to "svn import" - basically, import
> the (current) directory into the specified repo [...]

I wouldn't mind skipping the WC entirely and instead diff against BASE
on the spot while generating the commit. I don't know the import code
good enough to tell if your proposal is feasible.

The code to do this would be more complicated. For example, it has to
handle a number of situations gracefully, such as
files-turned-to-directories, to be useful for my backup purposes.

> svn import --takeover http://foo.bar.com/myproject/trunk

I think --takeover would be a bad name for your proposal, at least if
you still think it should be suitable for my needs.

'--replace' is better IMO, it indicates that the entire structure in
the repository should be replaced, including deleting files that
doesn't exist in the folder you're pointing 'import' at.

> [...] and then do the equivalent of a checkout in that directory

I have no use of the checkout once the changes have been committed to
the repository.
(I don't see how starting to checkout files fit with the 'import'
concept either..)

> to import the named directory and setup a WC there.

I have zero interest in setting up the WC after commit time, so that
wouldn't work for me.

> Also, if checkout gets support for --takeover, it should be super-
> easy to add it to import as well.

Really?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 18 16:30:35 2006