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

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

From: Michael Sweet <mike_at_easysw.com>
Date: 2006-04-18 16:49:45 CEST

Molle Bestefich wrote:
> 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.

OK, then we *are* thinking of two separate use cases, then.

I thought you wanted to start with an existing directory containing
config files/whatever and import them into a Subversion repo so that
they would be managed/versioned by Subversion.

It sounds more like you want to manage them as a "vendor branch"
but not actually use them "live" from the repo. I *think* there
is a Python script included with Subversion that might already do
what you want, but nothing is jumping out at me when I look...

>> [...] 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?

Yes, it would amount to import and then checkout in the same
directory.

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products           mike at easysw dot com
Internet Printing and Document Software          http://www.easysw.com
---------------------------------------------------------------------
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:50:34 2006

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.