On 01/30/18 09:36, ThierryIT wrote:
Hi,
Why are you closing a ticket before knowing if the modification you have made,
to correct the bug, is working ? I mean, why can't you wait for the user to add
the modification and see if it is working or not ?
Once a dev or contributor provides a fix that he/she thinks solves an
issue there is usually no reason to keep the issue open, or else the
issue tracker would be cluttered with fixed but open issues waiting to
be confirmed/closed by their reporter.
As exemple: ticket #3501 is closed, but even if I have followed the instruction, the problem is not solved, but the ticket is closed ...
Either you're now hitting a bug that has nothing to do with your
original issue or Marek thought he fixed the bug but made a mistake. If
it's the former simply open another issue. If it's the latter, I'd send
Marek a friendly email, or I would create a new issue pointing to the
wrongly solved older one.
How to re-open it ?
You can't, it looks like it's a github shortcoming. Had you taken 2 secs
to websearch it, you'd have found:
https://stackoverflow.com/questions/21333654/how-to-re-open-an-issue-in-github#21333938
first hit, no need to even click the link, the answer is at the top of
the search page: "you cannot re-open your own issues if a repo
collaborator closed them".
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/0a307dad-53a9-2728-8592-762f2b18fbaa%40maa.bz.
For more options, visit https://groups.google.com/d/optout.
