www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-3689) rsync access to git mirrors of svn repositories
Date Thu, 16 Jun 2011 08:31:47 GMT

    [ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050291#comment-13050291

Dawid Weiss commented on INFRA-3689:

I compared .config files on both repos -- I used 


and it should have been


After that, svn rebase seems to work fine. I'll double check just to make sure, but thanks
for help and apologies for this false alarm.

> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>                 Key: INFRA-3689
>                 URL: https://issues.apache.org/jira/browse/INFRA-3689
>             Project: Infrastructure
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Git, Subversion
>            Reporter: Dawid Weiss
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone
from such a repository. This means that while you can do git pulls, you can't do git svn dcommit,
which would be such a nice feature to have. I've tried to do it several times and failed and
I know of a few other people that couldn't do it either. 
> A simple solution to this problem would be to expose git repositories using rsync; this
would allow folks to mirror the full repository, including svn metadata, and then rebase/
dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using
wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true
to bare=false. Works like a charm.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message