> Ok, I'm not really sure what you mean. You can do an xcopy /Y to confirm
> overwriting existing files. I think the cp command has an equivalent option
> on Linux.
>
>
No, I mean if an XCOPY like thing is used wouldn't that lead to a situation
in which the .svn folders were overwritten? Wouldn't that obviate the
point? Or do I not understand your suggestion?
>
>
> ------------------------------
>
> *From:* Elaine Angelino [mailto:elaine.angelino_at_gmail.com]
> *Sent:* Wednesday, January 14, 2009 4:02 PM
> *To:* users_at_subversion.tigris.org
> *Cc:* Daniel Yamins
> *Subject:* Re: Automatically updated code/data directories
>
>
>
>
>
> On Wed, Jan 14, 2009 at 1:12 PM, Bob Archer <Bob.Archer_at_amsi.com> wrote:
>
> > Basically, can we just copy out the .svn directory in D (and the .svns
> > inside any dirtectories in D), and then simply copy them back in after
> the
> > re-making of D? Will this properly preserve the SVN control of the
> > files, and the relevant SVN repository information?
>
> Two possibilities I can think of.
>
> 1. Is it possible to generate D in a non-destructive way rather than
> deleting and recreating the full directory?
>
> 2. Generate D to a work area rather than the Working copy. Then copy it
> into the working copy folder.
>
> BOb
>
>
>
> Bob, thanks for this (I also work with Dan on this problem). As for 1,
> -- we could do something like copy out the .svn directory before the
> recreation event, and then copy it back in after. I think that other than
> something like that, basically we can't (and don't want to) generate D in a
> non-desctructive way.
>
> As for 2 -- wouldn't the copy have to be on a file-by-file basis, as
> opposed to a directory-tree copy?
>
> Elaine
>
>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1029114
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-27 21:45:01 CET