Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DB30110B5E for ; Mon, 27 Jan 2014 18:39:35 +0000 (UTC) Received: (qmail 51035 invoked by uid 500); 27 Jan 2014 18:39:34 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 50995 invoked by uid 500); 27 Jan 2014 18:39:34 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 50987 invoked by uid 99); 27 Jan 2014 18:39:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jan 2014 18:39:34 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [129.79.1.188] (HELO hartman.uits.indiana.edu) (129.79.1.188) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jan 2014 18:39:26 +0000 X-IronPort-AV: E=Sophos;i="4.95,730,1384318800"; d="scan'208,217";a="109779127" Received: from mssg-relay.indiana.edu ([129.79.1.73]) by irpt-internal-relay.indiana.edu with ESMTP; 27 Jan 2014 13:39:03 -0500 Received: from hartman.uits.indiana.edu (belushi.uits.indiana.edu [129.79.1.188]) by mssg-relay.indiana.edu (8.14.7/8.14.4/IU Messaging Team) with ESMTP id s0RIcxqi019447 for ; Mon, 27 Jan 2014 13:39:04 -0500 X-IronPort-AV: E=Sophos;i="4.95,730,1384318800"; d="scan'208,217";a="105865877" Received: from burns.uits.indiana.edu (HELO mail-relay.iu.edu) ([129.79.1.202]) by irpt-internal-relay.indiana.edu with ESMTP; 27 Jan 2014 13:39:02 -0500 Received: from 149-160-241-133.dhcp-bl.indiana.edu (149-160-241-133.dhcp-bl.indiana.edu [149.160.241.133]) (authenticated bits=0) by mail-relay.iu.edu (8.14.7/8.14.4/IU Messaging Team) with ESMTP id s0RId2XJ003820 for ; Mon, 27 Jan 2014 13:39:02 -0500 Message-ID: <52E6A7C6.5030109@iu.edu> Date: Mon, 27 Jan 2014 13:39:02 -0500 From: Marlon Pierce User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: dev@airavata.apache.org Subject: Fwd: [jira] [Commented] (INFRA-7242) Migrate Airavata from SVN to Git; Use svngit2jira References: In-Reply-To: X-Forwarded-Message-Id: Content-Type: multipart/alternative; boundary="------------060909000402090207070705" X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------060909000402090207070705 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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) 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) --------------060909000402090207070705 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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)


--------------060909000402090207070705--