From: David Bremner <david@tethera.net>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Cc: tomi.ollila@iki.fi
Subject: Re: [PATCH] test: copyright information updates
Date: Sun, 01 May 2016 21:49:51 -0300 [thread overview]
Message-ID: <87y47t707k.fsf@zancas.localnet> (raw)
In-Reply-To: <1460736374-10238-1-git-send-email-tomi.ollila@iki.fi>
Tomi Ollila <tomi.ollila@iki.fi> writes:
> # Copyright (c) 2005 Junio C Hamano
> +# Copyright (c) 2010-today Notmuch Developers
I don't what to think about this. The convention I am familiar with
for date ranges is roughly that documented here:
https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html
The tl;dr is that the years or ranges document the last significant
change.
On the other hand, I'd say most notmuch code has the copyright date
it is created, and that is never changed.
So I'd say go with creation date, or some actual date ranges that we
will probably forget to update.
OK, I agree it's nit picky. But it's a nit picky patch ;).
d
next prev parent reply other threads:[~2016-05-02 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 16:06 [PATCH] test: copyright information updates Tomi Ollila
2016-05-02 0:49 ` David Bremner [this message]
2016-05-02 4:07 ` Tomi Ollila
-- strict thread matches above, loose matches on Subject: below --
2016-05-06 15:41 Tomi Ollila
2016-05-19 11:07 ` David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y47t707k.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).