[gdal-dev] sandbox access for non-commiters
antonio.valentino at tiscali.it
Thu Oct 6 17:27:15 EDT 2011
Il 06/10/2011 23:03, Mateusz Loskot ha scritto:
> On 06/10/11 21:52, Antonio Valentino wrote:
>> Il 06/10/2011 22:01, Etienne Tourigny ha scritto:
>>> Thanks for the information. It seems that using git-svn is more
>>> suited for working locally, and then commiting back to the svn repos,
>>> or as an easy way to stay in-sync with the main repos (like you do).
>> IMHO the trick is using a separate branch for developing new features in
>> order to be able to use git freely.
>> When the job is done one should just rebase (locally) on the branch in
>> sync with svn and use git-svn to push hanges back into svn.
>> The weak point in the workflow is the initial cloning of the svn repo.
> Indeed, because every developer aiming in the git svn workflow
> has to do this initial step on his own. AFAIK, there is no way to
> centralise it.
> Best regards,
I'm wondering if there is some way to use a svn dump for the initial
setup of the git repo.
The svn dump could be downloaded (in compressed form) via FTP in a way
that is by far faster than the initial git svn fetch
Another option is to make available a pre-loaded git repo in compressed
Developers that want to use git should download and uncompress the
pre-loaded repo and re-sync using git-svn for getting last svn commits.
More information about the gdal-dev