www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Stitcher (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-11794) Migrate Qpid C++ to Git
Date Mon, 23 May 2016 18:51:12 GMT

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

Andrew Stitcher commented on INFRA-11794:
-----------------------------------------

That sounds like a good approach to explore. As long as the previous svn branch/tag history
is still accessible I think it'll be fine to just import the current svn trunk into git. Then
we can do whatever reorganisation of the tree in the new git repo.

Having said that if we are going to lose the tag/branch history anyway, we could happily just
start with a simplified tree that starts at the current

qpid/trunk/qpid/cpp level as the root in the new repo.

> Migrate Qpid C++ to Git
> -----------------------
>
>                 Key: INFRA-11794
>                 URL: https://issues.apache.org/jira/browse/INFRA-11794
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Git, Subversion
>            Reporter: Justin Ross
>            Assignee: Chris Lambertus
>
> The Apache Qpid project would like to request migration of the Qpid C++ code to a Git
repository.  This code was formerly one piece of a larger project, but it is now being split
out as standalone.
> A vote concerning this was made on the Qpid users list at [1], with the result available
at [2]. 
> The existing code is available in Subversion at: 
> http://svn.apache.org/repos/asf/qpid/trunk/qpid/cpp
> The existing codebase is in use for other components as well, so if anything is made
read-only in the process, it should be only the tree under /asf/qpid/trunk/qpid/cpp.
> We'd like the primary branch under Git to be "master" (not "trunk").  We'd like the Git
repository name to be "qpid-cpp".
> The repo currently has commits emails sent to our commits list [3], and gitsvn2jira integration
enabled for its JIRA project [4]. We would like these features to to be similarly enabled
for the new Git repo. 
> [1] Vote: http://qpid.2158936.n2.nabble.com/VOTE-Migrate-Qpid-C-and-Qpid-Python-to-Git-tp7642642.html
> [2] Result: http://qpid.2158936.n2.nabble.com/RESULT-VOTE-Migrate-Qpid-C-and-Qpid-Python-to-Git-tt7643013.html
> [3] Commits list: commits@qpid.apache.org 
> [4] JIRA project: https://issues.apache.org/jira/browse/QPID 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message