Issue 4888: git-cl: update status to Started for existing issues (issue 301920043 by nine.fierce.ball...@gmail.com)

2016-06-06 Thread nine . fierce . ballads
Reviewers: , Description: Issue 4888: git-cl: update status to Started for existing issues Please review this at https://codereview.appspot.com/301920043/ Affected files (+1, -0 lines): M allura_issues.py Index: allura_issues.py diff --git a/allura_issues.py b/allura_issues.py index d7b05

Re: PATCHES: Countdown for June 6th

2016-06-06 Thread Dan Eble
Thanks. Is there a good reason not to let the git-cl upload script set the status to Started? >>> >>> git-cl already does that. >> >> It didn’t for these two issues. > > Maybe that happens (not) when uploading to an already existing issue? > For newly created issues at least I did no

Re: PATCHES: Countdown for June 6th

2016-06-06 Thread David Kastrup
Dan Eble writes: >> On Jun 6, 2016, at 16:52 , David Kastrup wrote: >> >> Dan Eble writes: >> >>> On Jun 6, 2016, at 08:39 , David Kastrup wrote: Dan Eble writes: > Also, I submitted a couple patches that do not appear in your list. > Did I miss a step somewhere? >>

Re: PATCHES: Countdown for June 6th

2016-06-06 Thread Dan Eble
> On Jun 6, 2016, at 16:52 , David Kastrup wrote: > > Dan Eble writes: > >> On Jun 6, 2016, at 08:39 , David Kastrup wrote: >>> >>> Dan Eble writes: >>> Also, I submitted a couple patches that do not appear in your list. Did I miss a step somewhere? https://sourceforge

Re: PATCHES: Countdown for June 6th

2016-06-06 Thread Dan Eble
On Jun 6, 2016, at 08:39 , David Kastrup wrote: > > Dan Eble writes: > >> Also, I submitted a couple patches that do not appear in your list. >> Did I miss a step somewhere? >> >> https://sourceforge.net/p/testlilyissues/issues/2232/ >> https://sourceforge.net/p/testlilyissues/issues/3945/ >

Re: PATCHES: Countdown for June 6th

2016-06-06 Thread David Kastrup
Dan Eble writes: > On Jun 6, 2016, at 08:39 , David Kastrup wrote: >> >> Dan Eble writes: >> >>> Also, I submitted a couple patches that do not appear in your list. >>> Did I miss a step somewhere? >>> >>> https://sourceforge.net/p/testlilyissues/issues/2232/ >>> https://sourceforge.net/p/te

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

2016-06-06 Thread James Lowe
Hosoda-san, On 06/06/16 14:44, Masamichi Hosoda wrote: I've tried some Japanese fonts with `-dgs-load-fonts' option. [...] So most Japanese fonts can not be used with `-dgs-load-fonts' option. Any idea why this is so? Could you contact the gs people by filing a bug report so that we get an e

Re: PATCHES: Countdown for June 6th

2016-06-06 Thread James Lowe
On 06/06/16 13:39, David Kastrup wrote: Dan Eble writes: Also, I submitted a couple patches that do not appear in your list. Did I miss a step somewhere? https://sourceforge.net/p/testlilyissues/issues/2232/ https://sourceforge.net/p/testlilyissues/issues/3945/ Status "Started" rather than "

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

2016-06-06 Thread Werner LEMBERG
>> Any idea why this is so? Could you contact the gs people by filing >> a bug report so that we get an explanation? > > If I understand correctly, there is four issues at least. [...] Thanks for your analysis. Werner ___ lilypond-devel mailin

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

2016-06-06 Thread Masamichi Hosoda
>> I've tried some Japanese fonts with `-dgs-load-fonts' option. [...] >> >> So most Japanese fonts can not be used with `-dgs-load-fonts' >> option. > > Any idea why this is so? Could you contact the gs people by filing a > bug report so that we get an explanation? If I understand correctly,

Re: PATCHES: Countdown for June 6th

2016-06-06 Thread David Kastrup
Dan Eble writes: > Also, I submitted a couple patches that do not appear in your list. > Did I miss a step somewhere? > > https://sourceforge.net/p/testlilyissues/issues/2232/ > https://sourceforge.net/p/testlilyissues/issues/3945/ Status "Started" rather than "Accepted". Changed that right now

Re: PATCHES: Countdown for June 6th

2016-06-06 Thread Dan Eble
On Jun 6, 2016, at 05:30 , David Kastrup wrote: > > James Lowe writes: > >> Hello, >> >> Here is the current patch countdown list. The next countdown will be on >> June 9th. >> >> A quick synopsis of all patches currently in the review process can be >> found here: >> >> http://philholmes.ne

Re: Issue 4789: Note_performer: articulate events (issue 298330043 by d...@gnu.org)

2016-06-06 Thread dak
On 2016/06/05 18:18:23, ht wrote: This looks great! Even though this question has little relevance to these code changes, I can't resist asking whether you might have ideas about the best way to fix the "reverse" problem of ties attached to *individual notes of a chord* ending up ignored

Re: PATCHES: Countdown for June 6th

2016-06-06 Thread David Kastrup
James Lowe writes: > Hello, > > Here is the current patch countdown list. The next countdown will be on > June 9th. > > A quick synopsis of all patches currently in the review process can be > found here: > > http://philholmes.net/lilypond/allura/ > > Apologies for the huge list in countdown - we

PATCHES: Countdown for June 6th

2016-06-06 Thread James Lowe
Hello, Here is the current patch countdown list. The next countdown will be on June 9th. A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ Apologies for the huge list in countdown - we had a bit of a logjam a last week be