From: Thomas Gummerer <t.gummerer@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v1 1/2] t/README: remove mention of adding copyright notices
Date: Fri, 8 Dec 2017 20:47:36 +0000 [thread overview]
Message-ID: <20171208204736.GA25616@hank> (raw)
In-Reply-To: <20171205194937.GB8183@aiede.mtv.corp.google.com>
On 12/05, Jonathan Nieder wrote:
> Hi,
>
> Thomas Gummerer wrote:
>
> > We generally no longer include copyright notices in new test scripts.
> > However t/README still mentions it as something to include at the top of
> > every new script.
>
> Where can I read more about this change? Was it a deliberate change
> or something that simply happened?
I'm not sure if it was a deliberate change, I just noticed that most
new test files don't have a copyright notice anymore.
$ git grep "Copyright (c)" t/* | sed -E 's/.*?Copyright .c. ([[:digit:]]+).*?/\1/' | sort | uniq -c
61 2005
40 2006
55 2007
32 2008
31 2009
30 2010
10 2011
14 2012
4 2013
3 2014
1 2015
5 2016
While we may be adding less new test files, we definitely added a few
in 2017, for example t/t7521-ignored-mode.sh in 371c80c746 ("status:
test ignored modes", 2017-10-30), or t/t0025-crlf-renormalize.sh in
9472935d81 ("add: introduce "--renormalize"", 2017-11-16).
> Thanks,
> Jonathan
prev parent reply other threads:[~2017-12-08 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 20:20 [PATCH v1 1/2] t/README: remove mention of adding copyright notices Thomas Gummerer
2017-11-26 20:21 ` [PATCH v1 2/2] t/README: document test_cmp_rev Thomas Gummerer
2017-12-05 19:46 ` Jonathan Nieder
2017-12-05 19:49 ` [PATCH v1 1/2] t/README: remove mention of adding copyright notices Jonathan Nieder
2017-12-08 20:47 ` Thomas Gummerer [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171208204736.GA25616@hank \
--to=t.gummerer@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).