lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5591 git-cl u


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: Sat, 02 Nov 2019 18:26:26 -0000

no change

http://codereview.appspot.com/583120043


[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 06:26 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 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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]