From: Elijah Newren <newren@gmail.com>
To: Joel Holdsworth <jholdsworth@nvidia.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Tzadik Vanderhoof <tzadik.vanderhoof@gmail.com>,
Dorgon Chang <dorgonman@hotmail.com>,
Joachim Kuebart <joachim.kuebart@gmail.com>,
Daniel Levin <dendy.ua@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Luke Diamand <luke@diamand.org>, Ben Keene <seraphire@gmail.com>,
Andrew Oakley <andrew@adoakley.name>
Subject: Re: [PATCH v2 3/3] git-p4: add "Nvidia Corporation" to copyright header
Date: Sat, 11 Dec 2021 13:19:18 -0800 [thread overview]
Message-ID: <CABPp-BEyBLzWY2andDXZV6AgkQpnt1sp_rSThy84=qXMt2D8nA@mail.gmail.com> (raw)
In-Reply-To: <20211210153101.35433-4-jholdsworth@nvidia.com>
On Fri, Dec 10, 2021 at 12:30 PM Joel Holdsworth <jholdsworth@nvidia.com> wrote:
>
> The inclusion of the coorporate copyright is a stipulation of the
> company code release process.
> ---
> git-p4.py | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/git-p4.py b/git-p4.py
> index 5568d44c72..17e18265dc 100755
> --- a/git-p4.py
> +++ b/git-p4.py
> @@ -5,6 +5,7 @@
> # Author: Simon Hausmann <simon@lst.de>
> # Copyright: 2007 Simon Hausmann <simon@lst.de>
> # 2007 Trolltech ASA
> +# 2021 Nvidia Corporation
> # License: MIT <http://www.opensource.org/licenses/mit-license.php>
> #
> # pylint: disable=invalid-name,missing-docstring,too-many-arguments,broad-except
> --
> 2.33.0
Can we just get rid of all these copyright notices from all files in
Git? They're obviously out-of-date and not even close to an accurate
indicator of authorship. For example, builtin/branch.c has:
* Copyright (c) 2006 Kristian Høgsberg <krh@redhat.com>
* Based on git-branch.sh by Junio C Hamano.
Kristian only authored 1 patch for this file (though that one patch
was submitted and attributed to Lars Hjemli in c31820c26b ("Make
git-branch a builtin", 2006-10-23) with a note in the commit message
about Kristian being the real author). I added a simple replace
object to change the author attribution on Kristian's commit back to
him, and then...
Looking at shortlog, there are 86 different authors, with the top 7
having this many commits:
$ git shortlog -sn --no-merges -- builtin/branch.c builtin-branch.c | head -n 7
42 Junio C Hamano
37 Jeff King
30 Nguyễn Thái Ngọc Duy
16 Karthik Nayak
12 René Scharfe
11 Lars Hjemli
11 Ævar Arnfjörð Bjarmason
Looking at git blame, there are 61 different authors who have lines of
code surviving until today, with the top 7 being:
$ git blame -C -C builtin/branch.c | awk '{print $3 " " $4}' | sort |
uniq -c | sort -rn | head -n 7
139 (Junio C
129 (Nguyễn Thái
122 (Karthik Nayak
40 (Jeff King
38 (Kristian H�gsberg
36 (Sahil Dua
35 (René Scharfe
So the copyright notice is horribly misleading at best. It also seems
like the wrong way to figure out the answer to _any_ question I can
think of. (Some examples: "Who can review my changes to this file?",
"Who do I need to contact for permission to relicense?", "Who should I
praise for doing the work of making this code so great for me?", etc.)
-- in all cases, shortlog, log, and blame are better tools.
Can we just git rid of these lines entirely?
next prev parent reply other threads:[~2021-12-11 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 15:30 [PATCH v2 0/3] Transition git-p4.py to support Python 3 only Joel Holdsworth
2021-12-10 15:30 ` [PATCH v2 1/3] git-p4: remove support for Python 2 Joel Holdsworth
2021-12-12 17:50 ` Andrew Oakley
2021-12-12 22:01 ` Ævar Arnfjörð Bjarmason
2021-12-10 15:31 ` [PATCH v2 2/3] git-p4: eliminate decode_stream and encode_stream Joel Holdsworth
2021-12-10 15:31 ` [PATCH v2 3/3] git-p4: add "Nvidia Corporation" to copyright header Joel Holdsworth
2021-12-10 18:57 ` Luke Diamand
2021-12-11 21:19 ` Elijah Newren [this message]
2021-12-13 0:11 ` brian m. carlson
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='CABPp-BEyBLzWY2andDXZV6AgkQpnt1sp_rSThy84=qXMt2D8nA@mail.gmail.com' \
--to=newren@gmail.com \
--cc=andrew@adoakley.name \
--cc=dendy.ua@gmail.com \
--cc=dorgonman@hotmail.com \
--cc=git@vger.kernel.org \
--cc=jholdsworth@nvidia.com \
--cc=joachim.kuebart@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=luke@diamand.org \
--cc=seraphire@gmail.com \
--cc=tzadik.vanderhoof@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).