|
From: | Auto mailings of changes to Lily Issues via Testlilyissues-auto |
Subject: | [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5591 git-cl upload to existing SourceForge issue gives error 404 |
Date: | Sun, 03 Nov 2019 13:27:54 -0000 |
It was necessary to have a LilyPond ticket to test the git-cl changes, but I'm closing this as "Invalid" because it wasn't a LilyPond issue per se. git-cl was fixed by https://github.com/gperciva/git-cl/pull/5 .
[issues:#5591] git-cl upload to existing SourceForge issue gives error 404
Status: Invalid
Created: Sat Nov 02, 2019 04:33 PM UTC by Dan Eble
Last Updated: Sun Nov 03, 2019 06:04 AM 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 address@hidden 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 address@hidden https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Prev in Thread] | Current Thread | [Next in Thread] |