I see that patchy did not like my patch set 3 for issue 4299 (fails to apply
to current master). I'm guessing that this is the same thing we ran into
with issue 4258, since both involve adding new images. (James manually
tested 4258, which went through just fine.)
I don't anticipate adding
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: google-code-nore...@google.com
Date: Fri, Mar 13, 2015 at
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
On Fri, Mar 13, 2015 at 12:04 PM, David Kastrup d...@gnu.org 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
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
Graham Percival gra...@percival-music.ca 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
David Kastrup wrote Friday, March 13, 2015 11:51 AM
Subject: Re: Fwd: Google Code shutting down
Graham Percival gra...@percival-music.ca writes:
In addition to moving the issues, the issue handling scripts would
need to be updated. Things like git-cl, patchy, and the whole
Han-Wen Nienhuys hanw...@gmail.com 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
Trevor Daniels t.dani...@treda.co.uk writes:
Han-Wen, you wrote Friday, March 13, 2015 1:45 PM
On Fri, Mar 13, 2015 at 1:37 PM, Trevor Daniels t.dani...@treda.co.uk
wrote:
Two questions:
(a) how do we take a copy of this data base to keep it safe,
including all the follow-up
On Fri, Mar 13, 2015 at 1:37 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
David Kastrup wrote Friday, March 13, 2015 11:51 AM
Subject: Re: Fwd: Google Code shutting down
Graham Percival gra...@percival-music.ca writes:
In addition to moving the issues, the issue handling scripts would
Han-Wen, you wrote Friday, March 13, 2015 1:45 PM
On Fri, Mar 13, 2015 at 1:37 PM, Trevor Daniels t.dani...@treda.co.uk 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
11 matches
Mail list logo
