----- Original Message -----
From: "Dan Eble" <d...@faithful.be>
To: "Daniel Eble" <d...@faithful.be>
Cc: "David Kastrup" <d...@gnu.org>; <lilypond-devel@gnu.org>
Sent: Wednesday, June 08, 2016 10:45 PM
Subject: Re: PATCHES: Countdown for June 6th
Thanks. Is there a good reason not to let the git-cl upload script
set the status to Started?
...
I think I see in allura_issues.py where it would have to be done, and I
have a reasonable guess how to do it. If there is no reason that setting
the status to Started for an existing issue would be in
convenient, I’ll give it a try.
I believe I’ve fixed it with the git-formatted patch attached to
https://sourceforge.net/p/testlilyissues/issues/4888/ .
What is the protocol for making changes to git-cl? Is anyone willing to
take it from here?
—
Dan
If you create a pull request on github, I accept it and the changes can then
be pulled by users.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
