[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Allura/SourceForge to Gitlab migration
From: |
Karlin High |
Subject: |
Re: Allura/SourceForge to Gitlab migration |
Date: |
Mon, 9 Apr 2018 12:56:57 -0500 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
On 4/9/2018 11:06 AM, Federico Bruni wrote:
I don't want to revamp this old discussion:
http://lists.gnu.org/archive/html/lilypond-devel/2013-10/msg00095.html
http://lists.gnu.org/archive/html/lilypond-devel/2013-10/msg00140.html
I should have read those BEFORE making my other post.
Current obstacle is that there's no way to import Allura/SourceForge
issues into Gitlab. This is the issue to follow:
https://gitlab.com/gitlab-org/gitlab-ce/issues/45007
If you have a Gitlab account, click on the thumb up icon, as popular
issues should have higher chances to be tackled sooner than later.
Created account, upvoted the issue. Thanks for pointing this out.
--
Karlin High
Missouri, USA
- Allura/SourceForge to Gitlab migration, Federico Bruni, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration,
Karlin High <=
- Re: Allura/SourceForge to Gitlab migration, James Lowe, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Urs Liska, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Carl Sorensen, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Federico Bruni, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Urs Liska, 2018/04/09