[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUnet-developers] some bugs to be closed
From: |
ng0 |
Subject: |
Re: [GNUnet-developers] some bugs to be closed |
Date: |
Sun, 2 Jul 2017 09:51:36 +0000 |
ng0 transcribed 2.3K bytes:
> We can close this as notabug: https://gnunet.org/bugs/view.php?id=4146
> as there is nothing we can do it about it.
>
> We should close https://gnunet.org/bugs/view.php?id=4907 unless this
> isn't fixed. I have seen the code from the patch jah sent in the
> repository so I assume it is fixed as I ran into different testsuite
> failures.
>
> 2 people confirmed that this is fixed and we should close it:
> https://gnunet.org/bugs/view.php?id=5006
>
> This just leave 1 open bug then which is assigned to what we
> should rename to 0.11 because of the many breaking changes
> compared to 0.10.1.
> --
> ng0
> GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
> GnuPG: https://n0is.noblogs.org/my-keys
> https://www.infotropique.org https://krosos.org
Christian Grothoff commented on issue 0004907:
ng0: can you try _resolving_ instead of closing?
It wasn't possible, unless you have to reassign the
bug to the person who should close it. Next time I
will try that first.
With closing I meant resolving.
Thanks!
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org
signature.asc
Description: PGP signature