lilypond-devel
[Top][All Lists]
Advanced

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

Re: [PATCH] Remove routing information from Grob_info


From: David Kastrup
Subject: Re: [PATCH] Remove routing information from Grob_info
Date: Thu, 28 Apr 2016 20:18:26 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)

James <address@hidden> writes:

[git cl, Rietveld, Ubuntu 16.04]

> Well I do get an issue but not quite the same as yours.

[...]

> Issue updated. URL: http://codereview.appspot.com/294410043
> We were not able to associate this patch with a tracker issue.
> Please enter a valid tracker issue number
> (or enter nothing to create a new issue): [I just hit return and enter
> 'nothing']
>
> Error code 403
> Failed URL was https://sourceforge.net/rest/p/test/lilyissues/issues//new
> Failed data was
> ticket_form.summary=and+again%21&ticket_form.custom_fields._patch=new&ticket_form.custom_fields._type=Enhancement&ticket_form.description=and+again%21%0A%0Ahttp%3A%2F%2Fcodereview.appspot.com%2F294410043&access_token=fdbfca60801262365480&ticket_form.status=Started

There is a double slash in the URL close to the end: issues//new.  Maybe
that has something to do with it?

I think I get further than that: my failure occurs when uploading the
"base files" for an issue, the diff itself still arrives on Rietveld.
But without the base files, the side-by-side patch review does not work,
making Rietveld pretty pointless.

> I've compared all the various files and settings with the machine I am
> on now (that does work and uses 15.04 LTS) and I cannot see any
> differences.
>
> So I am at a bit of a loss.

Slash?

-- 
David Kastrup



reply via email to

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