Hi Trevor,
yes, I guess I never asked to be on that list. My last commit was
pre-Rietveld and pre-Allura, I think; and it's unlikely that
contributions from my side will come more often in the foreseeable
future (except for one more patch "in the pipeline", waiting for a
cleanup and documentation).
So I guess it's not really worth to give me any other status than other
occasional users. On the other hand, do whatever is the most convenient
for you - handling a lonesome patch every other year manually or adding me.
Cheers,
Alexander
On 2016-12-14 16:28, Trevor Daniels wrote:
Alexander, you wrote Wednesday, December 14, 2016 12:32 PM
On 2016-12-14 13:15, James wrote:
On 13/12/16 20:10, perpeduumimmob...@gmail.com wrote:
Reviewers: ,
Message:
add choral and choral-cautionary accidental style
...
Please review this at https://codereview.appspot.com/311430043/
Affected files (+151, -1 lines):
M Documentation/notation/pitches.itely
M ly/engraver-init.ly
M scm/music-functions.scm
_______________________________________________
Does this have an associated tracker item or do we need to create one
for you?
https://sourceforge.net/p/testlilyissues/issues/?source=navbar
I don't think git-cl created one; I received some error message but I
thought it related to the known and documented "no automatic
notification" after patch upload. But obviously, I mis-configured
git-cl's Allura bearer token...
Please create one if you don't mind; I will have a look at the
configuration for my next upload.
AFAICS you don't have developer status at SourceForge. Have you
ever asked to be added as a developer? That would explain
the failure.
To fix it please send me (or post to the list) your SourceForge
identifier and I'll add you.
Trevor
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
