From: Christoph Hellwig <hch@lst.de>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: Christoph Hellwig <hch@lst.de>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Qu Wenruo <wqu@suse.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] btrfs: split the bio submission path into a separate file
Date: Tue, 13 Sep 2022 07:08:29 +0200 [thread overview]
Message-ID: <20220913050829.GA29304@lst.de> (raw)
In-Reply-To: <PH0PR04MB7416C3ED5D9F5732E5C4D5D09B449@PH0PR04MB7416.namprd04.prod.outlook.com>
On Mon, Sep 12, 2022 at 03:27:10PM +0000, Johannes Thumshirn wrote:
> On 12.09.22 16:11, Christoph Hellwig wrote:
> > +// SPDX-License-Identifier: GPL-2.0
> > +/*
> > + * Copyright (C) 2007 Oracle. All rights reserved.
> > + * Copyright (C) 2022 Christoph Hellwig.
> > + */
>
> IIRC David does try to get rid of all the per-company copyright
> statements for new files.
We just had that discussion in another thread - there really is no
basis for getting rid of them. In fact talking to lawyers, most
of them thing we should have more of them, not less.
next prev parent reply other threads:[~2022-09-13 5:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 14:11 move the low-level btrfs_bio code into a separate file (resent) Christoph Hellwig
2022-09-12 14:11 ` [PATCH 1/2] btrfs: split the bio submission path into a separate file Christoph Hellwig
2022-09-12 15:27 ` Johannes Thumshirn
2022-09-13 5:08 ` Christoph Hellwig [this message]
2022-09-21 9:40 ` David Sterba
2022-09-22 6:39 ` Christoph Hellwig
2022-09-12 14:11 ` [PATCH 2/2] btrfs: move repair_io_failure to bio.c Christoph Hellwig
2022-09-12 15:28 ` Johannes Thumshirn
2022-09-12 18:02 ` move the low-level btrfs_bio code into a separate file (resent) Josef Bacik
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=20220913050829.GA29304@lst.de \
--to=hch@lst.de \
--cc=Johannes.Thumshirn@wdc.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.