All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Hannes Reinecke <hare@suse.de>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Mike Christie <mchristi@redhat.com>,
	Christoph Hellwig <hch@lst.de>,
	target-devel@vger.kernel.org
Subject: Re: [PATCH 3/3] scsi: target: Change nab@linux-iscsi.org into nab@kernel.org
Date: Tue, 19 Sep 2023 08:09:05 -0700	[thread overview]
Message-ID: <3cf27172-6fda-469a-be30-69916b35ee79@acm.org> (raw)
In-Reply-To: <98ca06fa-229b-460f-96bb-2d8b50dfc45e@suse.de>

On 9/19/23 01:11, Hannes Reinecke wrote:
> Hmm. I'm not sure if replacing the original e-mail addresses in the 
> copyright portions of the source file is the way to go. For figuring
> out which e-mail address one should consult the MAINTAINERS file; I
> would treat the e-mail addresses in the copyright primarily as a
> reference to the original author and the company he worked for at
> that time. So I'd rather not change that.
> 
> But that's personal opinion, of course. I'm not a lawyer.

Thanks Hannes for having taken a look. I'm not a lawyer either. This is
what I found by searching on the web for "How to write a copyright
notice?":
* The standard format for a copyright notice is (1) a copyright symbol
followed by (2) a date, (3) the name of the author and (4) a statement
of rights.
* None of the guides that were written by a lawyer mentioned the
inclusion of an email address in the copyright notice.

The Bard software told me the following: "Legally speaking, the email
address is not required for a copyright notice to be valid. Copyright
protection is automatic in most countries, and a copyright notice is
simply a way of notifying others of your ownership rights. However,
there are some potential benefits to including an email address in your
copyright statement.

For example, if someone infringes on your copyright, you can use your
email address to contact them and ask them to stop. You can also use
your email address to file a DMCA takedown notice with a hosting
provider or search engine."

Anyway, unless someone has another opinion, I will revert the email 
address changes in the copyright statements when I repost this patch
series.

Bart.

      reply	other threads:[~2023-09-19 15:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 21:59 [PATCH 0/3] Replace references to linux-iscsi.org Bart Van Assche
2023-09-18 21:59 ` [PATCH 1/3] scsi: target: Remove the references to http://www.linux-iscsi.org/ Bart Van Assche
2023-09-19  8:06   ` Hannes Reinecke
2023-09-18 21:59 ` [PATCH 2/3] scsi: target: Remove linux-iscsi.org copyright statements Bart Van Assche
2023-09-19  8:07   ` Hannes Reinecke
2023-09-18 21:59 ` [PATCH 3/3] scsi: target: Change nab@linux-iscsi.org into nab@kernel.org Bart Van Assche
2023-09-19  8:11   ` Hannes Reinecke
2023-09-19 15:09     ` Bart Van Assche [this message]

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=3cf27172-6fda-469a-be30-69916b35ee79@acm.org \
    --to=bvanassche@acm.org \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=martin.petersen@oracle.com \
    --cc=mchristi@redhat.com \
    --cc=target-devel@vger.kernel.org \
    /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.