airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marlon Pierce <marpi...@iu.edu>
Subject Fwd: [jira] [Commented] (INFRA-7242) Migrate Airavata from SVN to Git; Use svngit2jira
Date Mon, 27 Jan 2014 18:39:02 GMT
SVN is now read only.


Marlon


-------- Original Message --------
Subject: 	[jira] [Commented] (INFRA-7242) Migrate Airavata from SVN to
Git; Use svngit2jira
Date: 	Mon, 27 Jan 2014 18:37:38 +0000 (UTC)
From: 	Jake Farrell (JIRA) <jira@apache.org>
To: 	mpierce@cs.indiana.edu



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

Jake Farrell commented on INFRA-7242:
-------------------------------------

I've started the migration, setting your svn repository as read only. I will notify you once
it has been migrated to git-wip and have you verify it. 

> Migrate Airavata from SVN to Git; Use svngit2jira
> -------------------------------------------------
>
>                 Key: INFRA-7242
>                 URL: https://issues.apache.org/jira/browse/INFRA-7242
>             Project: Infrastructure
>          Issue Type: Task
>            Reporter: Marlon Pierce
>            Assignee: Jake Farrell
>
> The Apache Airavata PMC requests that its SVN repository be migrated to Git, preserving
our commit history.  Our SVN repo is http://svn.apache.org/repos/asf/airavata/.  We plan to
keep our current source code directory structure.
> We also want to use svngit2jira to link git commit messages to Jira tickets. These should
be triggered in the standard way (including "Airavata-XYZ" in the commit message). Please
let us know if this requires a separate INFRA jira ticket or if this can all be done at once.
 
> Thanks--



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)




Mime
View raw message