[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesos-dev
Subject:    [jira] [Resolved] (MESOS-70) De-activate Github.com/mesos/mesos git repository
From:       "Charles Reiss (Resolved) (JIRA)" <jira () apache ! org>
Date:       2012-03-30 20:55:29
Message-ID: 309893267.39880.1333140929099.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/MESOS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Charles Reiss resolved MESOS-70.
--------------------------------

    Resolution: Fixed

I think this is done; the current contents of the github.com/mesos/mesos master \
branch are just a README.md file saying Mesos has moved (which is not a friendly \
message for those pulling, but works). The Wiki there appears to reference the \
official Apache repos.  
> De-activate Github.com/mesos/mesos git repository
> -------------------------------------------------
> 
> Key: MESOS-70
> URL: https://issues.apache.org/jira/browse/MESOS-70
> Project: Mesos
> Issue Type: Task
> Reporter: Andy Konwinski
> 
> It is confusing to keep this repository around, though it is nice to have the \
> code's git history available since that got a bit messed up in the move to Apache \
> SVN. Rather than trying to keep this repository in sync with the Apache \
> repositories, we should remove it. After it goes away, it would be best if github \
> allowed us to provide a helpful message when people who currently have it set up as \
> their "origin" remote repo do git remote update or git pull. Also, it would be nice \
> if we could set up github to forward folks who visit the old repo in the web \
> interface on to the Apache repo. Also, the download directions on the wiki \
> (currently at github.com/mesos/mesos/wiki) reference this repo right now (saying \
> not to use it). When it is gone, that reference should be removed as well.

--
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

        


[prev in list] [next in list] [prev in thread] [next in thread]