On Wed, Sep 14, 2022 at 01:28:27PM +0200, Juergen Gross wrote:
> On 13.09.22 17:52, Roger Pau Monné wrote:
> > On Fri, Jul 22, 2022 at 02:31:28PM +, Andrew Cooper wrote:
> > > I've been cross-checking licensing details, and we have some problems.
> > >
> > > 1) We install xen/include/public/CO
On 13.09.22 17:52, Roger Pau Monné wrote:
On Fri, Jul 22, 2022 at 02:31:28PM +, Andrew Cooper wrote:
I've been cross-checking licensing details, and we have some problems.
1) We install xen/include/public/COPYING into /usr/include/xen/COPYING,
which is not common practice. The installed fi
On Fri, Jul 22, 2022 at 02:31:28PM +, Andrew Cooper wrote:
> I've been cross-checking licensing details, and we have some problems.
>
> 1) We install xen/include/public/COPYING into /usr/include/xen/COPYING,
> which is not common practice. The installed file is mostly useless
> because it dis
On Fri, 22 Jul 2022, Andrew Cooper wrote:
> I'm also intending to start using SDPX identifiers to save on all the
> boilerplate. They're already used elsewhere.
I just wanted to add that adding/using SPDX is important and came up
quite a few times in Linux Foundation discussions recently [1]. Lin
I've been cross-checking licensing details, and we have some problems.
1) We install xen/include/public/COPYING into /usr/include/xen/COPYING,
which is not common practice. The installed file is mostly useless
because it discusses files based on their xen.git paths.
2) We actually use the MIT he
