hello,
On 09/04/15 16:10, Werner LEMBERG wrote:
But the situation overall is a nuisance.
Might be worth keeping a weather eye on Launchpad, as this is free
software and is currently in the process of gaining git support:
https://help.launchpad.net/Code/Git
Interesting!
It's been a while since I last used it, but it has a nice
combination of issue tracking, code review and hosting features.
AFAICS it'll also support file attachments to issues, so should be
able to support copying the .png's from Lilypond's current issue
tracker.
While I don't like bzr, the launchpad interface for reporting bugs and
the like looks OK to me. So yes, this is a possible solution.
Werner
I think this has already been mentioned but just to chip in that it
isn't just about reviewing patches, patches have to be tested too. While
I can (and have) done manual patch testing in the past before the patchy
scripts were created - it does add significant amounts of time on my
part to test patches this way and would mean that the times during a
given day of the week when I could test any random new patch (or three)
would be severely reduced.
Just sayin'
James
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
