On Thu, Oct 6, 2011 at 4:23 PM, David Weintraub <qazwart_at_gmail.com> wrote:
>> On Thu, Oct 6, 2011 at 1:51 PM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
>>
>>>> >> What about using "svngit"? We could have an automated process that
>>>> >> pulls data from the Subversion repository in the U.S. and creates a
>>>> >> local Git repository in India using "svngit'. This could be done when
>>>> >> there's no one in the Indian office. Developers could then checkout
>>>> >> and commit their changes to their local Git repository. In the middle
>>>> >> of the night, the Git repository could then push its changes to
>>>> >> Subversion using "gitsvn" Is this a possibility?
>
> On Thu, Oct 6, 2011 at 3:49 PM, Les Mikesell <lesmikesell_at_gmail.com> wrote:
>> I don't have experience with using git-svn myself, but it seems to be
>> designed to handle that scenario.
>
> Svn-git was mainly designed to allow you to checkpoint your work
> without checking in code you know might not work.
>
> What I am thinking is something a bit more radical: Using Git as a
> local repository for a remote Subversion repository. Now, you're
> talking about 10 to 20 or more users in your remote site using Git,
> pushing their changes to the local central Git repository, and then
> having that central Git repository sync itself back to the Subversion
> repository. You're hope is that the site that has the Subversion
> repository isn't doing to many changes while the remote site is
> active. And, the remote site isn't active while the local site is
> committing changes into Subversion.
Have you seen this?
http://subgit.com/
It is something the guys that make SVNKit have been working on.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2011-10-06 22:32:12 CEST