Phil's script that runs from his website gets the 'first' (I think) coderieview
link it finds - as the convention was the link was always in the summary
somewhere. The main thing is that the ticket is on the list, and I always check
the ticket and the coderieview - in case there is something special I have to
do or there is some requirement on how the patch can be tested. Phil's scraping
was more for the Patch Meister (me) than anything if only to save me having to
manually create a liste each time for the group when I send the emails out.
Mark H did a script for what Phil's website does before we moved from Google to
Source forge for our Tracker, I think it is somewhere in the git-cl repo still
- look for 'patchy' - but it was never adapted for Source Forge.
---
** [issues:#5591] git-cl upload to existing SourceForge issue gives error 404**
**Status:** Started
**Created:** Sat Nov 02, 2019 04:33 PM UTC by Dan Eble
**Last Updated:** Sat Nov 02, 2019 07:22 PM UTC
**Owner:** Dan Eble
> when uploading a first patch set, git-cl asks for a sourceforge issue number.
> If a new issue is created, everything is fine but when you choose an existing
> issue, there is some 404 error and the Rietveld link is not added to the sf
> issue—resulting in a missing Rietveld link on
> www.philholmes.net/lilypond/allura/ Does anybody know why that is happening?
https://lists.gnu.org/archive/html/lilypond-devel/2019-09/msg00111.html
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
