# git-svn capabilities

3 messages from 2007-12-09 to 2007-12-09. Participants: Pedro Melo, Adam Roben.
Thread: https://gitlist.dev/t/11208

## Pedro Melo, 2007-12-09 08:20

Subject: git-svn capabilities
Message-ID: <DB0B4F17-9E06-4C28-933E-FDEF9BAD6539@simplicidade.org>
URL: https://gitlist.dev/e/DB0B4F17-9E06-4C28-933E-FDEF9BAD6539%40simplicidade.org

```
Hi,

I've been following along the gcc/git thread with interest and I've  
used Harvey Harrison recipe

http://article.gmane.org/gmane.comp.version-control.git/67253

with success on several svn repos.

One thing that I'm not sure yet if it is possible to do is this:

can I have a single central git repo that tracks the svn repo, allow  
several developers to use clone to copy that repo, and each one of  
them (after proper manual configuration) uses dcommit to push back to  
svn?

All the recipes so far assume that each developer has to go through  
the initial git-svn fetch and have a copy of the entire SVN repo, and  
that seems wasteful to me.

Thanks,
-- 
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: melo@simplicidade.org
Use XMPP!

```

## Adam Roben, 2007-12-09 08:37

Subject: Re: git-svn capabilities
Message-ID: <475BA95F.7040403@apple.com>
URL: https://gitlist.dev/e/475BA95F.7040403%40apple.com
In-Reply-To: <DB0B4F17-9E06-4C28-933E-FDEF9BAD6539@simplicidade.org>

```
Pedro Melo wrote:
> Hi,
>
> I've been following along the gcc/git thread with interest and I've 
> used Harvey Harrison recipe
>
> http://article.gmane.org/gmane.comp.version-control.git/67253
>
> with success on several svn repos.
>
> One thing that I'm not sure yet if it is possible to do is this:
>
> can I have a single central git repo that tracks the svn repo, allow 
> several developers to use clone to copy that repo, and each one of 
> them (after proper manual configuration) uses dcommit to push back to 
> svn?
>
> All the recipes so far assume that each developer has to go through 
> the initial git-svn fetch and have a copy of the entire SVN repo, and 
> that seems wasteful to me.

The "Basic Examples" section of the git-svn man page describe how to do 
just that (though only for a single branch).

-Adam

```

## Pedro Melo, 2007-12-09 11:20

Subject: Re: git-svn capabilities
Message-ID: <80A466F9-B7D3-437B-8249-DE4E650CE276@simplicidade.org>
URL: https://gitlist.dev/e/80A466F9-B7D3-437B-8249-DE4E650CE276%40simplicidade.org
In-Reply-To: <475BA95F.7040403@apple.com>

```
Hi,

On Dec 9, 2007, at 8:37 AM, Adam Roben wrote:

> Pedro Melo wrote:
>> I've been following along the gcc/git thread with interest and  
>> I've used Harvey Harrison recipe
>>
>> http://article.gmane.org/gmane.comp.version-control.git/67253
>>
>> with success on several svn repos.
>>
>> One thing that I'm not sure yet if it is possible to do is this:
>>
>> can I have a single central git repo that tracks the svn repo,  
>> allow several developers to use clone to copy that repo, and each  
>> one of them (after proper manual configuration) uses dcommit to  
>> push back to svn?
>>
>> All the recipes so far assume that each developer has to go  
>> through the initial git-svn fetch and have a copy of the entire  
>> SVN repo, and that seems wasteful to me.
>
> The "Basic Examples" section of the git-svn man page describe how  
> to do just that (though only for a single branch).

Sorry, missed that completely :)

Best regards,
-- 
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: melo@simplicidade.org
Use XMPP!

```
