From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Lu Fengqi <lufq.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 04/10] btrfs-progs: undelete-subvol: introduce is_subvol_intact
Date: Mon, 7 May 2018 13:40:22 +0200 [thread overview]
Message-ID: <20180507114021.GA32018@suse.cz> (raw)
In-Reply-To: <9c7668bf-e5e1-44df-183f-e12b0d990422@gmx.com>
On Mon, May 07, 2018 at 10:20:57AM +0800, Qu Wenruo wrote:
> >>> +++ b/undelete-subvol.c
> >>> @@ -0,0 +1,53 @@
> >>> +/*
> >>> + * Copyright (C) 2018 Fujitsu. All rights reserved.
> >>
> >> IIRC David will remove all such copy right line.
> >> Is there some principle about this, David?
> >
> > Are you referring to this patchset that replace GPL boilerplate by SPDX?
> > https://patchwork.kernel.org/patch/10321621/
> >
> > However, I haven't seen a similar patch in btrfs-progs.
> >
>
> Nope, I mean David will remove the Copyright (C) line when applying.
> Although I'm not completely sure.
Removing copyright notices should not be done without an ack from all
parties and I don't remove the copyright notices from patches if
present.
I personally do not understand and see the point of the explicit
mentions if we have the signed-off by in git history. Also, when the
file is touched by many different people over time, the line 'copyright
by Evil Company' looks like all the credit goes to the single entitiy.
There's a point if the code is copied from another source, like the
test/sha* code that's from an RFC.
So, I decided to not care too much about the copyright line as long as
there's a signed-off and authorship is GPL compatible.
next prev parent reply other threads:[~2018-05-07 11:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 7:06 [PATCH v2 00/10] undelete subvolume offline version Lu Fengqi
2018-03-27 7:06 ` [PATCH v2 01/10] btrfs-progs: copy btrfs_del_orphan_item from kernel Lu Fengqi
2018-03-27 7:06 ` [PATCH v2 02/10] btrfs-progs: extract btrfs_link_subvol from btrfs_mksubvol Lu Fengqi
2018-04-18 5:02 ` Qu Wenruo
2018-05-07 2:00 ` Lu Fengqi
2018-03-27 7:06 ` [PATCH v2 03/10] btrfs-progs: use btrfs_find_free_dir_index to find free inode index Lu Fengqi
2018-04-18 5:04 ` Qu Wenruo
2018-03-27 7:06 ` [PATCH v2 04/10] btrfs-progs: undelete-subvol: introduce is_subvol_intact Lu Fengqi
2018-04-18 5:12 ` Qu Wenruo
2018-05-07 2:03 ` Lu Fengqi
2018-05-07 2:20 ` Qu Wenruo
2018-05-07 11:40 ` David Sterba [this message]
2018-05-07 12:16 ` Qu Wenruo
2018-03-27 7:06 ` [PATCH v2 05/10] btrfs-progs: undelete-subvol: introduce recover_dead_root Lu Fengqi
2018-04-18 5:16 ` Qu Wenruo
2018-05-07 2:04 ` Lu Fengqi
2018-03-27 7:06 ` [PATCH v2 06/10] btrfs-progs: undelete-subvol: introduce link_subvol_to_lostfound Lu Fengqi
2018-04-18 5:21 ` Qu Wenruo
2018-05-07 2:06 ` Lu Fengqi
2018-03-27 7:06 ` [PATCH v2 07/10] btrfs-progs: undelete-subvol: introduce btrfs_undelete_intact_subvols Lu Fengqi
2018-04-18 5:28 ` Qu Wenruo
2018-05-07 2:12 ` Lu Fengqi
2018-03-27 7:06 ` [PATCH v2 08/10] btrfs-progs: undelete-subvol: add undelete-subvol subcommand Lu Fengqi
2018-04-18 5:32 ` Qu Wenruo
2018-05-07 2:16 ` Lu Fengqi
2018-03-27 7:06 ` [PATCH v2 09/10] btrfs-progs: tests: add testcase for undelete-subvol Lu Fengqi
2018-04-18 5:42 ` Qu Wenruo
2018-05-07 2:28 ` Lu Fengqi
2018-03-27 7:06 ` [PATCH v2 10/10] btrfs-progs: undelete-subvol: update completion and documentation Lu Fengqi
2018-04-18 3:04 ` [PATCH v2 00/10] undelete subvolume offline version Lu Fengqi
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=20180507114021.GA32018@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lufq.fnst@cn.fujitsu.com \
--cc=quwenruo.btrfs@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).