Thomas Morley <thomasmorle...@gmail.com> writes: > 2017-03-26 11:11 GMT+02:00 David Kastrup <d...@gnu.org>: >> Thomas Morley <thomasmorle...@gmail.com> writes: >> >>> 2017-03-26 10:06 GMT+02:00 David Kastrup <d...@gnu.org>: >>> >>>> 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 _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
