that’s why you don’t fork it, you re-upload it when you hear it’s stirring
that’s why you don’t fork it, you re-upload it when you hear it’s stirring
If only I could show segfaul stack tracetrough looped macros.
It breaks VSCode (it would be hilarious if I wasn’t the author of said macros).
Shouldn’t there be ‘?’ before t? Like:
maybe because I don’t know how some command receives piped output?
Also some commands don’t work with pipe, so kowing how pipe itsef is implemented is just a fraction of information.
In short incus has Apache 2.0 copyright licene that states:
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole
While AGPL v3.0 that Canonical just adopted states:
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
. . .
You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy …
Meaning if incus uses any part of Canonicals source their code can’t be licenced under Apache but rather AGPL v3.0, which pulls any other derivative of incus.
deleted by creator
which breaks if you checkout on windows