Heyo,
I finished my midterms and am working on my GSOC application. Please let me
know if I've grasped this right:
If I understand correctly, export involves converting natural lilypond
scheme data into SXML so we can use Guile to reduce the problem of XML
conversion. And for import, it's the sam
On 3/13/15 5:10 AM, "Graham Percival" wrote:
>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 discu
LGTM.
https://codereview.appspot.com/219780044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Assaf, you wrote Sunday, March 15, 2015 3:53 AM
>
> On 03/14/2015 01:57 PM, Trevor Daniels wrote:
>> I confirm this works, at least for the one instance I tried.
>> I guess now we need to write a script which parses the JSON
>> file to find the attachment parameters and then to wget them
>> using
Hello,
Here is the current patch countdown list. The next countdown will be on
March 18th.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch
_
Hello Trevor,
Thanks for the information.
On 03/14/2015 01:57 PM, Trevor Daniels wrote:
I confirm this works, at least for the one instance I tried.
I guess now we need to write a script which parses the JSON
file to find the attachment parameters and then to wget them
using the assembled url.
