Displaying 3 results from an estimated 3 matches for "d6d1704".
Did you mean:
d61705
2019 Sep 07
2
[libnbd PATCH] maint: Update reference to license info
...The LGPL requires that the user also receive a copy of the GPL, since
anyone can upgrade their copy from LGPL to GPL. Does that mean we
should ship a copy of COPYING alongside COPYING.LIB?
README | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/README b/README
index c591f4a..d6d1704 100644
--- a/README
+++ b/README
@@ -29,7 +29,8 @@ LICENSE
The software is copyright © Red Hat Inc. and licensed under the GNU
Lesser General Public License version 2 or above (LGPLv2+). See
-‘LICENSE’ for details.
+the file ‘COPYING.LIB’ for details. The examples are under a very
+liberal lic...
2019 Sep 07
0
Re: [libnbd PATCH] maint: Update reference to license info
...eive a copy of the GPL, since
> anyone can upgrade their copy from LGPL to GPL. Does that mean we
> should ship a copy of COPYING alongside COPYING.LIB?
>
> README | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/README b/README
> index c591f4a..d6d1704 100644
> --- a/README
> +++ b/README
> @@ -29,7 +29,8 @@ LICENSE
>
> The software is copyright © Red Hat Inc. and licensed under the GNU
> Lesser General Public License version 2 or above (LGPLv2+). See
> -‘LICENSE’ for details.
> +the file ‘COPYING.LIB’ for details. Th...
2019 Sep 17
7
[PATCH libnbd 0/5] interop: Check that LIBNBD_TLS_ALLOW works against nbdkit.
I was a little surprised to find that LIBNBD_TLS_ALLOW worked out of
the box, so I had to examine the logs whereupon I saw the magic
message ...
libnbd: debug: nbd1: nbd_connect_command: server refused TLS (policy), continuing with unencrypted connection
I don't believe this path has ever been tested before.
It's possible the tests could be improved if they actually checked for
this