[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3601 in lilypond: Docs: new MIDI output capabi
|
From: |
lilypond |
|
Subject: |
Re: [Lilypond-auto] Issue 3601 in lilypond: Docs: new MIDI output capability: panning, etc. |
|
Date: |
Tue, 29 Jul 2014 14:25:35 +0000 |
Comment #6 on issue 3601 by address@hidden: Docs: new MIDI output capability:
panning, etc.
http://code.google.com/p/lilypond/issues/detail?id=3601
[Side question: Locally, I have also a patch to add MIDI "expression"
to this set of context properties. What's the recommended policy to
open a new issue for this patch? As I'm only an occasional
contributor, do I first need to ask for permission for opening an issue
on the lilypond-devel mailing list, or can I just go ahead and run the
git cl commands to create the new issue?]
Properly entering and classifying an issue should be left to developers or
the bug squad. If you use git-cl, you are a developer by definition.
--
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