www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-5065) Migrate flume codebase from svn to git.
Date Sun, 29 Jul 2012 10:22:33 GMT

     [ https://issues.apache.org/jira/browse/INFRA-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jukka Zitting updated INFRA-5065:

    Status: Waiting for user  (was: Waiting for Infra)

The writable Git repository is now available at https://git-wip-us.apache.org/repos/asf/flume.git
and contains all changes up to revision 1366581 from yesterday.

Your svn repository is still writable, so you may decide yourself when to make the final switch
to Git. Once you're ready, you can pull latest changes from git.apache.org/flume.git and push
them to git-wip-us to sync up the git repository.

Let me know when you've done this, and I'll switch off the automatic sync from svn.
> Migrate flume codebase from svn to git.
> ---------------------------------------
>                 Key: INFRA-5065
>                 URL: https://issues.apache.org/jira/browse/INFRA-5065
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Hari Shreedharan
> The Apache Flume community has voted and decided to move the primary source control for
Flume from svn to git. Please create a git repo for flume and migrate the code to that.
> The Vote thread: http://apache.markmail.org/thread/t5c3m23njuafryce
> The Vote Result thread: http://apache.markmail.org/thread/b3uz3dm2rgyeuikg
> The Discussion thread: http://apache.markmail.org/thread/fkkraooktzxelbr2
> Please note that both git.apache.org/flume.git and https://github.com/apache/flume seem
to be behind the svn repo. The github mirro is usually behind by several hours, while the
apache git mirror is slow by a few minutes to a couple of hours.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message