Updates:
Status: Fixed
Labels: -Patch-push Fixed_2_17_23
Comment #7 on issue 3450 by [email protected]: \addlyrics doesn't work with
TabStaff
http://code.google.com/p/lilypond/issues/detail?id=3450
Pushed to staging as
commit 0c9726a0d0093db2e31ec9ba80a7f9df150a5827
Author: Thomas Morley <[email protected]>
Date: Mon Jul 15 12:18:18 2013 +0200
Issue 3450: \addlyrics doesn't work with TabStaff
More details about limitation of \addlyrics in
Documentation/notation/vocal.itely
Add a hint, that \addlyrics does not work with TabStaff
Signed-off-by: David Kastrup <[email protected]>
Could you try in future not to invent a different title line for the commit
message/review? When there is a mismatch, it means that I have the onus of
trying to create a commit message that corresponds reasonably to both issue
and code review, and that's a definite nuisance. I'd prefer to be able to
just use the review message. Usually when you create a commit and then use
git cl for creating both code review and issue, the issue title is taken
from the first line of the commit message (which should be followed by a
blank line) and this should not even be an issue.
--
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
