org
> Onderwerp: Re: Another patch
>
> On May 10, 2020, at 08:11, lilyp...@de-wolff.org wrote:
> >
> > I did replace all implicit casts to an int by a inline function,
> > checking if the value is valid, and then casting to int.
> >
> > Together wi
On May 10, 2020, at 08:11, lilyp...@de-wolff.org wrote:
>
> I did replace all implicit casts to an int by a inline function, checking if
> the value is valid, and then casting to int.
>
> Together with my previous patch now all but one compiler warnings are
> solved.
Jaap,
I love the fact
I did replace all implicit casts to an int by a inline function, checking if
the value is valid, and then casting to int.
Together with my previous patch now all but one compiler warnings are
solved.
Remark: I do not have git rights on the lilypond tree, so someone else
should merge those
LGTM, I think. I'm not completely certain what I'm reviewing here.
I'm content to have this (whatever it is) go through, but in the future
could you:
- keep you changes in a separate git branch (locally)
- run: git cl upload origin/master
while on that local git branch.
Yes, this will
Il giorno ven, 29/06/2012 alle 11.00 +, gra...@percival-music.ca ha
scritto:
LGTM, I think. I'm not completely certain what I'm reviewing here.
I'm content to have this (whatever it is) go through, but in the future
could you:
- keep you changes in a separate git branch (locally)
-
John Mandereau john.mander...@gmail.com writes:
Il giorno ven, 29/06/2012 alle 11.00 +, gra...@percival-music.ca ha
scritto:
LGTM, I think. I'm not completely certain what I'm reviewing here.
I'm content to have this (whatever it is) go through, but in the future
could you:
- keep
LGTM. One tweak, then it can be pushed directly to staging.
http://codereview.appspot.com/6354044/diff/1/Documentation/contributor/administration.itexi
File Documentation/contributor/administration.itexi (right):
, also contains another patch for CG
Oops, the two commits have been merged into one, but they were initially
two.
CG: improve Patchy documentation
CG: Add LILYPOND_BUILD_DIR environment variable, fix issues 2604 and
2524.
Please review this at http://codereview.appspot.com/6354044/
Affected
Juergen == Juergen Reuter [EMAIL PROTECTED] writes:
except I find it harder to read. What do you think is the
advantage of yours over mine?
Juergen Your approach
a = re.sub ( '-', '- ', a)# split words with -
Juergen applies a rule which holds for most
On Mon, 2 Oct 2006, Laura Conrad wrote:
I just tested it and in actual code, yours seems to do the same thing
mine does,
N.B.: There should be a minor difference in the handling of white space
before/after the hyphen, which however is not essential, I guess.
except I find it harder to
Juergen == Juergen Reuter [EMAIL PROTECTED] writes:
a = re.sub ( '-', '- ', a)# split words with -
+a = re.sub ( ' - - ', ' -- ', a) # unless was originally --
Juergen Just being curious:
Juergen Maybe I am totally wrong (since I do not know the abc format in
a = re.sub ( '-', '- ', a)# split words with -
+a = re.sub ( ' - - ', ' -- ', a) # unless was originally --
Just being curious:
Maybe I am totally wrong (since I do not know the abc format in detail),
but shouldn't this be rather something like
a = re.sub (
Translation of MIDI tempo is now the new sytax. Also the annoying
erroneous error message about not being able to translate a numerator
of 1 is fixed.
? scripts/out
Index: ChangeLog
===
RCS file:
13 matches
Mail list logo
