public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/2] Rewrite fsx-linux test
Date: Mon, 20 Nov 2023 17:50:45 +0100	[thread overview]
Message-ID: <20231120165045.GA40415@pevik> (raw)
In-Reply-To: <a54b0968-fca8-49aa-91a2-4135e8bd231e@suse.com>

Hi Andrea,

> Hi!

> On 11/1/23 11:53, Cyril Hrubis wrote:
> > Hi!
> > > > +++ b/testcases/kernel/fs/fsx-linux/fsx-linux.c
> > > > @@ -1,1353 +1,392 @@
> > > > +// SPDX-License-Identifier: GPL-2.0-or-later
> > > >   /*
> > > >    * Copyright (C) 1991, NeXT Computer, Inc.  All Rights Reserverd.
> > > > - * Copyright (c) 1998-2001 Apple Computer, Inc. All rights reserved.
> > > > - *
> > > > - * @APPLE_LICENSE_HEADER_START@
> > > > - *
> > > > - * The contents of this file constitute Original Code as defined in and
> > > > - * are subject to the Apple Public Source License Version 1.1 (the
> > > > - * "License").  You may not use this file except in compliance with the
> > > > - * License.  Please obtain a copy of the License at
> > > > - * http://www.apple.com/publicsource and read it before using this file.
> > > I wonder if we can switch from APSL-1.1 to GPL-2.0-or-later
> > > https://spdx.org/licenses/APSL-1.1.html

> > > "This is a complete rewrite of the old test." may justify that.
> > The test was written from scratch based loosely on what the original
> > stress test did, so I would say that the new license is okay.

> > But I suggested adding "Based on fxs.c test by Next Computer, Inc."
> > instead of the copyright lines, since I suppose that once we add these
> > copyrights we have to keep the original license.
> This is explained in the description.

If you mean the commit message description, that's IMHO not enough.
Statements like this are added into the source code header so that people who
download tarballs see it as well.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2023-11-20 16:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 11:01 [LTP] [PATCH v2 0/2] Rewrite fsx-linux Andrea Cervesato
2023-10-30 11:01 ` [LTP] [PATCH v2 1/2] Rewrite fsx-linux test Andrea Cervesato
2023-11-01 10:34   ` Petr Vorel
2023-11-01 10:53     ` Cyril Hrubis
2023-11-01 11:11       ` Petr Vorel
2023-11-20 15:55       ` Andrea Cervesato via ltp
2023-11-20 16:50         ` Petr Vorel [this message]
2023-11-20 18:24           ` Andrea Cervesato via ltp
2023-11-13 16:05   ` Petr Vorel
2023-11-14 10:31     ` Andrea Cervesato via ltp
2023-10-30 11:01 ` [LTP] [PATCH v2 2/2] Remove fsx runtest suite Andrea Cervesato
2023-11-13 15:56   ` Petr Vorel
2023-11-13 16:02   ` Petr Vorel
2023-11-28 18:26     ` Petr Vorel
2023-11-29  9:42       ` Andrea Cervesato via ltp
2023-11-13 15:57 ` [LTP] [PATCH v2 0/2] Rewrite fsx-linux Petr Vorel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231120165045.GA40415@pevik \
    --to=pvorel@suse.cz \
    --cc=andrea.cervesato@suse.com \
    --cc=ltp@lists.linux.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox