From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] common/sfc_efx: update copyright year
Date: Fri, 12 Mar 2021 16:57:56 +0100 [thread overview]
Message-ID: <1814295.Ebq3lEQrT6@thomas> (raw)
In-Reply-To: <43888872-56db-974c-056d-a337ed22e48d@intel.com>
12/03/2021 15:57, Ferruh Yigit:
> On 3/11/2021 10:00 AM, Andrew Rybchenko wrote:
> > Bump copyright year to 2021.
> >
> > Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>
> Series applied to dpdk-next-net/main, thanks.
>
>
> Not really it is a trouble for me but do we really need these year updates,
> what happens if we update the year only when we touch that file?
We don't think about updating the year each time we touch a file,
and it would be annoying.
> cc'ed a few more people may know more about copyright year.
I am not sure the copyright can end at a date if not mentioned.
And I don't think it has already been an issue for any Open Source SW.
I think the most important is to mark the first year.
Personnaly I consider the starting date is enough,
so I never extend the copyright after the original year.
Note: I avoid the usual "IANAL but". Oops just did it ;)
prev parent reply other threads:[~2021-03-12 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 10:00 Andrew Rybchenko
2021-03-11 10:00 ` [dpdk-dev] [PATCH 2/2] net/sfc: " Andrew Rybchenko
2021-03-12 14:57 ` [dpdk-dev] [PATCH 1/2] common/sfc_efx: " Ferruh Yigit
2021-03-12 15:57 ` Thomas Monjalon [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=1814295.Ebq3lEQrT6@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=stephen@networkplumber.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 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).