infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gruno (JIRA)" <>
Subject [jira] [Commented] (INFRA-7524) migrate Apache Subversion project over to the git repo
Date Tue, 01 Apr 2014 11:18:15 GMT


Daniel Gruno commented on INFRA-7524:

Ack, we'll get started on this issue.
The git repo (both the original subversion and the new git) will be read-only until you have
verified that the contents and structure is okay.
Once you verify that (in this ticket), I'll open up the repo for write access and expect you
to use that repo instead of the subversion directory.

For starters, let me know when you are satisfied with the go-ahead (please inform your committers
than the subversion repo will also be read-only during this process), and I'll start the process:
1) Set svn repo to read-only
2) Initialize a new read-only git repo from the subversion repo
3) Have you (or the PMC) verify that the new git repo is sane
4) Open up write-access to the new git repo
5) Open up write access to the subversion repo (which is still required for web sites with

> migrate Apache Subversion project over to the git repo
> ------------------------------------------------------
>                 Key: INFRA-7524
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Git
>            Reporter: Greg Stein
> Grrrr... vote passed. Not happy, but here we go:
> Infra: please migrate our repository at /repos/asf/subversion/ over to the Git repository
> We already have the mirror at But that has always been there as a read-only
mirror (along with the copy over to GitHub). Will the git repo be at (is
it *still* considered -wip "work in progress"?)
> Not sure what else you guys need. Haven't exactly studied up on the migration process.
Please let me know.
> (tho I'm up late here now and need to sleep soon; others from the PMC will be able to

This message was sent by Atlassian JIRA

View raw message