seems reasonable changes if ok
ALAN D JOHNSON
On Sun, 18 Dec 2005 12:36:05 -0500 Phillip Susi <psusi@cfl.rr.com> wrote:
attached mail follows:
I'm not quite sure I followed exactly what you were saying, but if you
were sugesting svn switching a WC from one repository to the other, you
can't do that.
You can export from one repository then import and merge into the other,
but you loose the history information what way.
Chak wrote:
> I have a situation where an application in the office has been recently introduced to SVN, but it's earlier version is in the site where it undergoes changes, even as the office version evolves. I know this is very disorganised way of working but this is the reality. Now, if i wanted to help the teams synchronise, without using the internet based SVN due to certain constraints, will this approach work ?
>
> 1) Get the 'site version' on a periodical basis to office
> 2) Create a repository around it
> 3) Check it out to a folder called WC1
> 4) Switch the repository of WC1 to point to the repository of the team maintained in the office
> 5) Update and commit WC1
> 6) Export WC1 and take it to site and update the version
> 6.1) hope that the user does not face any regression issues.
>
> Assuming that we take the risk of 6.1 (regression), are the above steps a suitable workaround to the situation ?
>
> Thanks and Regards,
>
> Chakravarthy
>
>
> __________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 18 19:16:04 2005