On 13/03/15 12:51, David Kastrup wrote:
GitLab (like GitHub) does not run on free software. They have some
"community" version of their software freely available at least.
Gitorious was "eating its own dog food" with regard to running on their
free software version, but they have just been acqui
On Fri, Mar 13, 2015 at 4:40 PM, Trevor Daniels wrote:
>> have a look at
>>
>> https://code.google.com/p/support-tools/wiki/IssueExporterTool
>
> That is quite useful, thanks. I've exported the LilyPond Issues
> DB to a JSON file on my laptop. 5Mb. It seems complete as far
> as the text goes, b
Han-Wen, you wrote Friday, March 13, 2015 1:45 PM
> On Fri, Mar 13, 2015 at 1:37 PM, Trevor Daniels wrote:
>>
>> Two questions:
>>
>> (a) how do we take a copy of this data base to keep it safe,
>> including all the follow-up discussions? Making a CSV
>> copy just seems to download the i
"Trevor Daniels" writes:
> Han-Wen, you wrote Friday, March 13, 2015 1:45 PM
>
>> On Fri, Mar 13, 2015 at 1:37 PM, Trevor Daniels
>> wrote:
>>>
>>> Two questions:
>>>
>>> (a) how do we take a copy of this data base to keep it safe,
>>> including all the follow-up discussions? Making a CSV
On Fri, Mar 13, 2015 at 1:37 PM, Trevor Daniels wrote:
>
> David Kastrup wrote Friday, March 13, 2015 11:51 AM
> Subject: Re: Fwd: Google Code shutting down
>
>
>> Graham Percival writes:
>
>>> In addition to moving the issues, the "issue handling" sc
David Kastrup wrote Friday, March 13, 2015 11:51 AM
Subject: Re: Fwd: Google Code shutting down
> Graham Percival writes:
>> In addition to moving the issues, the "issue handling" scripts would
>> need to be updated. Things like git-cl, patchy, and the whole
>>
Graham Percival writes:
> On Fri, Mar 13, 2015 at 11:33:22AM +0100, Han-Wen Nienhuys wrote:
>> I can click the "export" button so all the issues are migrated to
>> github. Thoughts, ideas?
>>
>> Didn't someone setup a lilypond organization at github?
>
> There was some discussion about that, whi
On Fri, Mar 13, 2015 at 12:04 PM, David Kastrup wrote:
> I suspect that there will not be much hope for transferring the Rietveld
> reviews over into something Git-based and reasonably equivalent, but
> they are less important than getting everything out of the issue
> tracker.
Rietveld is not p
Han-Wen Nienhuys writes:
> I guess most of you have seen this by now.
Not really.
> I can click the "export" button so all the issues are migrated to
> github. Thoughts, ideas?
I don't really want LilyPond to move to GitHub. I prefer figuring out
what resources we would need from Savannah and
Am 13.03.2015 um 11:33 schrieb Han-Wen Nienhuys:
I guess most of you have seen this by now.
I can click the "export" button so all the issues are migrated to
github. Thoughts, ideas?
Didn't someone setup a lilypond organization at github?
Yes, that was Janek. But it was considered problematic
On Fri, Mar 13, 2015 at 11:33:22AM +0100, Han-Wen Nienhuys wrote:
> I can click the "export" button so all the issues are migrated to
> github. Thoughts, ideas?
>
> Didn't someone setup a lilypond organization at github?
There was some discussion about that, which spilled over to
gnu-hackers or g
I guess most of you have seen this by now.
I can click the "export" button so all the issues are migrated to
github. Thoughts, ideas?
Didn't someone setup a lilypond organization at github?
-- Forwarded message --
From:
Date: Fri, Mar 13, 2015 at 2:11 AM
Subject: Google Code shu
12 matches
Mail list logo
