Re: add choral and choral-cautionary accidental style (issue311430043by perpeduumimmob...@gmail.com)
Alexander, you wrote Thursday, December 15, 2016 3:51 PM > On 2016-12-15 13:34, Trevor Daniels wrote: > >> Adding you to the dev list is very little work, but you do have to >> get a SourceForge id and tell me what it is for me to do that. >> >> James probably is willing to undertake the work of creating an >> issue and servicing it on your behalf, but if you yourself are not >> known to Allura you will not be able to contribute to any discussion >> on _any_ issue - including those James has created on your behalf. > > Okay, makes sense. In this case, I guess it's reasonable to add me no > matter how much (or little) I will participate. I created an SF account > with username akobel. Added, giving you Developer status. Now you can update and create issues as well as read them. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: add choral and choral-cautionary accidental style (issue311430043by perpeduumimmob...@gmail.com)
On 2016-12-15 13:34, Trevor Daniels wrote: Alexander, you wrote Wednesday, December 14, 2016 11:49 PM 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. Adding you to the dev list is very little work, but you do have to get a SourceForge id and tell me what it is for me to do that. James probably is willing to undertake the work of creating an issue and servicing it on your behalf, but if you yourself are not known to Allura you will not be able to contribute to any discussion on _any_ issue - including those James has created on your behalf. Okay, makes sense. In this case, I guess it's reasonable to add me no matter how much (or little) I will participate. I created an SF account with username akobel. Cheers, Alexander ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: add choral and choral-cautionary accidental style (issue311430043by perpeduumimmob...@gmail.com)
Alexander, you wrote Wednesday, December 14, 2016 11:49 PM > 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. Adding you to the dev list is very little work, but you do have to get a SourceForge id and tell me what it is for me to do that. James probably is willing to undertake the work of creating an issue and servicing it on your behalf, but if you yourself are not known to Allura you will not be able to contribute to any discussion on _any_ issue - including those James has created on your behalf. Trevor > 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 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
