Re: github mirror of lilypond?

2020-01-17 Thread Erlend Aasland
Is there a reason _not_ to use GitHub for development/bugtracking/wiki/planning? The current dev model is, to put it mildly, and in lack of better words, cumbersome and archaic. GNU licences are AFAICS supported by GitHub, so that can’t be a showstopper. If we had a more modern development

reviewing granular commits?

2020-01-17 Thread Han-Wen Nienhuys
I just made a sequence of random bugfixes, which I cleanly committed in separate commits, but now I discovered that get squashed on review by git-cl. For the moment, I've put them here, https://github.com/hanwen/lilypond/commits/salzburg but it would be nice to have a more Git-native review

Re: sf issue tracker access

2020-01-17 Thread Trevor
Hi Han-Wen Great to have you back! You've now got Create and Update permissions along with Read in the SourceForge Issue Tracker. Trevor -- Original Message -- From: "Han-Wen Nienhuys" To: "lilypond-devel" Sent: 17/01/2020 23:02:18 Subject: sf issue tracker access Hi, i'm

github mirror of lilypond?

2020-01-17 Thread Han-Wen Nienhuys
It looks like https://github.com/lilypond was last updated in Jun 2019. If there was an automated mirror, it has stopped working. Could someone give it a kick again? -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen

sf issue tracker access

2020-01-17 Thread Han-Wen Nienhuys
Hi, i'm "hanwen" for the sourceforge bug tracker. Could someone give me write access? -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen

Re: Cleanup initialization of configure process (issue 549350043 by jonas.hahnf...@gmail.com)

2020-01-17 Thread jonas . hahnfeld
On 2020/01/17 07:35:45, Dan Eble wrote: I've run some builds with a writable source directory, and I'm fine with it. Feel free to move forward with the cleaner change. I'll submit a LilyDev pull request to cope with it. I'm not going to change this patch once more. We can keep it in mind