Updates:
Status: Verified
Comment #29 on issue 2348 by colingh...@gmail.com: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Verified that the commitish for this patch was part of release 2.15.34.
_
Updates:
Status: Fixed
Labels: -Patch-push Fixed_2_15_34
Comment #28 on issue 2348 by d...@gnu.org: Patch: Handling of open strings
in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Pushed as e31a76e94f59d00968ddfe95a92138b5df799a8e to staging.
___
Updates:
Labels: -Patch-countdown Patch-push
Comment #27 on issue 2348 by colinpkc...@gmail.com: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Counted down to 20120311, please push.
__
Updates:
Owner: m...@hohlart.de
Comment #26 on issue 2348 by m...@hohlart.de: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
(No comment was entered for this change.)
___
bug-lilypond m
Updates:
Labels: Patch-review
Comment #24 on issue 2348 by d...@gnu.org: Patch: Handling of open strings
in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348#c24
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
Comment #23 on issue 2348 by gra...@percival-music.ca: Patch: Handling of
open strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Marc: you need to have a google account. Contact Phil.
___
bug-lilypond mailing list
bug-l
Comment #22 on issue 2348 by pkx1...@gmail.com: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
You need permissions to change status, although if you use the recent
git-cl that is documented here:
http://lilypond.org/doc/v2.15/Document
Comment #21 on issue 2348 by m...@hohlart.de: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Am 08.03.2012 09:22, schrieb lilyp...@googlecode.com:
Am I allowed to set the status? Obviously, I am not the owner,
so I don't see a way to do a
Updates:
Labels: -Patch-needs_work Patch-new
Comment #20 on issue 2348 by d...@gnu.org: Patch: Handling of open strings
in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Uh Marc: after correcting a patch, you need to set its status to Patch-new
or it won't get tes
Comment #19 on issue 2348 by m...@hohlart.de: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Am 06.03.2012 11:20, schrieb lilyp...@googlecode.com:
Corrected. Sorry for the nuisance.
___
bug-li
Comment #18 on issue 2348 by m...@hohlart.de: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348#c18
Handling of open strings in tablature
This patch creates a switch called ignoreOpenStrings. When set to #f
(default), LilyPond handles open s
Updates:
Labels: Patch-needs_work
Comment #17 on issue 2348 by d...@gnu.org: Patch: Handling of open strings
in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348#c17
Patchy the autobot says: Patchy actually does not complain, but the diffs
show an inconsistent mixtur
Updates:
Status: Started
Owner: d...@gnu.org
Labels: -Patch-needs_work Patch-new
Comment #16 on issue 2348 by d...@gnu.org: Patch: Handling of open strings
in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
I think that Colin may be confusing this wit
Comment #15 on issue 2348 by m...@hohlart.de: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
I stumbled upon comment #12 - how does this patch interfere with Mike's
work?
Are there any reasons not to include this patch in one of the next
Comment #14 on issue 2348 by m...@hohlart.de: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Ok, so I changed excludeOpenStrings to restrainOpenStrings.
___
bug-lilypond mailing list
bug-lilypo
Comment #13 on issue 2348 by m...@hohlart.de: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348#c13
Handling of open strings in tablature
This patch creates a switch called ignoreOpenStrings. When set to #f
(default), LilyPond handles open s
Updates:
Labels: -Patch-push Patch-needs_work
Comment #12 on issue 2348 by colinpkc...@gmail.com: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
I see Mike wants to hold this one out of the sequence, so I'\ll put it
on "Needs-wor
Updates:
Labels: -Patch-countdown Patch-push
Comment #11 on issue 2348 by colinpkc...@gmail.com: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Counted down to 20120228, please push.
__
Comment #10 on issue 2348 by d...@gnu.org: Patch: Handling of open strings
in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Ok, seems like I am too stupid to make up my mind. It's not likely worth
stopping the countdown for that reason alone, but here is _another_
pro
Comment #9 on issue 2348 by d...@gnu.org: Patch: Handling of open strings
in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Ok, I am officially an idiot. It turns out that my assertion that
properties were usually defaulting to #f was totally wonkers if you take a
look
Comment #8 on issue 2348 by m...@hohlart.de: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348#c8
Handling of open strings in tablature
This patch creates a switch called ignoreOpenStrings. When set to #f
(default), LilyPond handles open str
Comment #6 on issue 2348 by m...@hohlart.de: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348#c6
Handling of open strings in tablature
This patch creates a switch called ignoreOpenStrings. When set to #f
(default), LilyPond handles open str
Updates:
Labels: Patch-review
Comment #5 on issue 2348 by julien.r...@gmail.com: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348#c5
Patchy the autobot says: LGTM.
___
bug-lilypond mailin
Updates:
Labels: -Patch-needs_work Patch-new
Comment #4 on issue 2348 by julien.r...@gmail.com: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
(No comment was entered for this change.)
Comment #3 on issue 2348 by m...@hohlart.de: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348#c3
Handling of open strings in tablature
This patch creates a switch called ignoreOpenStrings. When set to #f
(default), LilyPond handles open str
Comment #2 on issue 2348 by m...@hohlart.de: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348#c2
Handling of open strings in tablature
This patch creates a switch called ignoreOpenStrings. When set to #f
(default), LilyPond handles open str
Updates:
Labels: Patch-needs_work
Comment #1 on issue 2348 by d...@gnu.org: Patch: Handling of open strings
in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348#c1
Patchy the autobot says: /usr/local/tmp/lilypond/issue5695058_2001.diff:15:
trailing whitespace.
/usr
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2348 by m...@hohlart.de: Patch: Handling of open strings in
tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Handling of open strings in tablature
This patch creates a switch called ignoreOpenStrings. When
28 matches
Mail list logo
