[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 5099 - staging broken?
From: |
David Kastrup |
Subject: |
Re: Issue 5099 - staging broken? |
Date: |
Sun, 26 Mar 2017 13:30:25 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) |
Thomas Morley <address@hidden> writes:
> 2017-03-26 11:11 GMT+02:00 David Kastrup <address@hidden>:
>> Thomas Morley <address@hidden> writes:
>>
>>> 2017-03-26 10:06 GMT+02:00 David Kastrup <address@hidden>:
>>>
>>>> Backing out that patch from staging, and taking a further look.
>>>
>>> How to proceed?
>>> Upload a fixed patch for review?
>>
>> Probably.
>
> Meanwhile I tried to upload a fixed patch to
> https://sourceforge.net/p/testlilyissues/issues/5101/
> https://codereview.appspot.com/318680043/
>
> But I had closed the Rietveld-issue already, so I get from git-cl:
> [...]
> Issue creation errors: {'issue': ['This issue is closed (318680043)']}
>
> Nevertheless
> https://github.com/rietveld-codereview/rietveld/wiki
> says:
> 'Closing the Issue
> [...] An issue's owner can reopen the issue by unchecking the "Closed" box.'
>
> But I can't, the "Closed box" is not longer present.
The "Close" box isn't. I think editing the summary (possibly from the
"post comments" page) also permitted changing the "closed" status.
--
David Kastrup
Re: Issue 5099 - staging broken?, David Kastrup, 2017/03/26