Am 01.08.2012 13:02, schrieb Phil Holmes:
----- Original Message ----- From: "Marc Hohl" <m...@hohlart.de>
To: "David Kastrup" <d...@gnu.org>
Cc: <lilyp...@googlecode.com>; <codesite-nore...@google.com>;
<lilypond-devel@gnu.org>
Sent: Wednesday, August 01, 2012 11:46 AM
Subject: Re: [Lilypond-auto] Issue 1320 in lilypond:
Enhancement:user-customizable barlines through a Scheme interface.
Am 01.08.2012 09:51, schrieb David Kastrup:
Marc Hohl <m...@hohlart.de> writes:
Am 01.08.2012 03:42, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-countdown Patch-push
Comment #56 on issue 1320 by colinpkc...@gmail.com: Enhancement:
user-customizable barlines through a Scheme interface.
http://code.google.com/p/lilypond/issues/detail?id=1320
Counted down to 20120731, please push.
Pushed as
a1b73185eae2f07dfee3cfcac0a6f11a15075ffe
to staging.
If you have pushed a patch to staging, please go to the issue, write
the
comment that it has been pushed _there_, mark the issue as Fixed,
remove
the Patch-push label and replace it by Fixed_2_15_42 or whatever is
appropriate. if you are not sure about the version, you can check with
git show a1b73185eae2f07dfee3cfcac0a6f11a15075ffe:VERSION
in the top directory. The relevant upcoming version is detailed in
MAJOR_VERSION, MINOR_VERSION and PATCH_LEVEL (the other numbers are not
relevant for development).
I assumed that "fixed" is appropriate when the patch is in master,
not in staging,
so I would have waited until then.
This is normally only a matter of hours, so it's traditional to mark
it fixed when it's in staging. Of course, if it fails in being moved
to master, you'd need to change that...
In this case, the patch failed already once, so I hesitated to call it
"fixed", but ok, for the next patch I know what to do.
Regards,
Marc
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
