[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3710 in lilypond: NR 4.4.1 collisions
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 3710 in lilypond: NR 4.4.1 collisions |
Date: |
Wed, 25 Dec 2013 18:52:39 +0000 |
Updates:
Labels: -2_19_0 -Backport Fixed_2_19_0 Fixed_2_17_98
Comment #6 on issue 3710 by address@hidden: NR 4.4.1 collisions
http://code.google.com/p/lilypond/issues/detail?id=3710
Keith, please post the commit message or at least the commit id when fixing
a problem. It's not fun to dig through commit histories. Not for the bug
squad when verifying, and also not for me when backporting. Best to do
this together with changing the status to "Fixed" while the commit is still
fresh: that's when the information is available easiest.
It's triply annoying if the commit message does not mention the issue
number and is significantly different from the issue description.
Cherrypicked to stable/2.18 as
commit 1bd942245288557297e6e76ec124761ef5c768b6
Author: Keith OHara <address@hidden>
Date: Sat Dec 7 14:23:28 2013 -0800
documentation: staff-spacing, resolve collisions
The original commit id in 2.19.0 was
03c026361826478e7e19130f7ed732a243f38a63
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
- [Lilypond-auto] Issue 3710 in lilypond: NR 4.4.1 collisions, lilypond, 2013/12/07
- Re: [Lilypond-auto] Issue 3710 in lilypond: NR 4.4.1 collisions, lilypond, 2013/12/07
- Re: [Lilypond-auto] Issue 3710 in lilypond: NR 4.4.1 collisions, lilypond, 2013/12/08
- Re: [Lilypond-auto] Issue 3710 in lilypond: NR 4.4.1 collisions, lilypond, 2013/12/10
- Re: [Lilypond-auto] Issue 3710 in lilypond: NR 4.4.1 collisions, lilypond, 2013/12/13
- Re: [Lilypond-auto] Issue 3710 in lilypond: NR 4.4.1 collisions, lilypond, 2013/12/13
- Re: [Lilypond-auto] Issue 3710 in lilypond: NR 4.4.1 collisions,
lilypond <=