Re: Request for developer status on the issue tracker
On pe, 2016-01-08 at 16:36 +, Trevor Daniels wrote: > Heikki, you wrote Friday, January 08, 2016 4:18 PM > > > I still managed (like I always seem to do when I run git-cl with > > several months having passed since the last time...) to fail to > > submit > > a patch with git-cl fully successfully (*), so I had to create a > > new > > issue for the tracker (https://sourceforge.net/p/testlilyissues/iss > > ues/ > > 4730/) manually. I'm sorry if I didn't get the values of all > > metadata > > fields right when creating the issue - I'd be grateful for any help > > whether something still needs to be fixed there. > > Only the Owner field was missing, so I added your username, > and Accepted the Issue. Thank you! Heikki ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Request for developer status on the issue tracker
Heikki, you wrote Friday, January 08, 2016 4:18 PM > I still managed (like I always seem to do when I run git-cl with > several months having passed since the last time...) to fail to submit > a patch with git-cl fully successfully (*), so I had to create a new > issue for the tracker (https://sourceforge.net/p/testlilyissues/issues/ > 4730/) manually. I'm sorry if I didn't get the values of all metadata > fields right when creating the issue - I'd be grateful for any help > whether something still needs to be fixed there. Only the Owner field was missing, so I added your username, and Accepted the Issue. > (*) Failing with git-cl was simply my own fault, as I didn't anticipate > (remember) that git-cl would need to open a web browser in the middle > of the patch submission procedure - this didn't work well as I wasn't > logged on in a GUI session, and had to abort the script. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Request for developer status on the issue tracker
On pe, 2016-01-08 at 13:54 +, Trevor Daniels wrote: > > Added to Devs as requested. > > Trevor Thanks! I still managed (like I always seem to do when I run git-cl with several months having passed since the last time...) to fail to submit a patch with git-cl fully successfully (*), so I had to create a new issue for the tracker (https://sourceforge.net/p/testlilyissues/issues/ 4730/) manually. I'm sorry if I didn't get the values of all metadata fields right when creating the issue - I'd be grateful for any help whether something still needs to be fixed there. (*) Failing with git-cl was simply my own fault, as I didn't anticipate (remember) that git-cl would need to open a web browser in the middle of the patch submission procedure - this didn't work well as I wasn't logged on in a GUI session, and had to abort the script. -- Heikki Tauriainen ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Request for developer status on the issue tracker
Heikki Tauriainen wrote Friday, January 08, 2016 1:04 PM > I understand that running git-cl to create new issues requires > developer status on the issue tracker at Sourceforge. I've just > created a SourceForge account, and would kindly request developer > access to the issue tracker (if possible). My username at SourceForge > is "htlily". Hi Heikki Added to Devs as requested. You'll be known in issues as "H T LilyPond". Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Request for developer status on the issue tracker
Hi, I understand that running git-cl to create new issues requires developer status on the issue tracker at Sourceforge. I've just created a SourceForge account, and would kindly request developer access to the issue tracker (if possible). My username at SourceForge is "htlily". Thanks, Heikki ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
