Eric Blake, le jeu. 14 mars 2019 08:44:06 -0500, a ecrit:
> However, while it does not affect compilation, it DOES have legal
> ramification; I'd feel a lot better about having R-b on every patch,
Sure, I was just asking for the git commit path :) I don't think it's
useful to make it go through my
On 3/14/19 8:19 AM, Samuel Thibault wrote:
> Hello,
>
> Should this go through my tree, or perhaps it can be directly pushed to
> master by Peter since it's no-code-only-copyright changes?
I think this definitely qualifies as 4.0 material.
However, while it does not affect compilation, it DOES h
On 3/14/19 8:10 AM, Marc-André Lureau wrote:
> Hi,
>
> In order to make slirp a standalone project, the project must have a
> clear license, and be compatible with the GPL or LGPL.
>
> Since commit 2f5f89963186d42a7ded253bc6cf5b32abb45cec ("Remove the
> advertising clause from the slirp license")
Hi,
In order to make slirp a standalone project, the project must have a
clear license, and be compatible with the GPL or LGPL.
Since commit 2f5f89963186d42a7ded253bc6cf5b32abb45cec ("Remove the
advertising clause from the slirp license"), slirp is BSD-3. But new
files have been added under slirp
Hello,
Should this go through my tree, or perhaps it can be directly pushed to
master by Peter since it's no-code-only-copyright changes?
Samuel
Marc-André Lureau, le jeu. 14 mars 2019 14:10:41 +0100, a ecrit:
> In order to make slirp a standalone project, the project must have a
> clear license
