git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Frederic Tessier <ftessier@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Dangling copyright in git hook template
Date: Wed, 19 Jan 2022 11:49:28 -0800	[thread overview]
Message-ID: <xmqqbl07mrp3.fsf@gitster.g> (raw)
In-Reply-To: <CAB7QKarvGGjNf-bvuKqwnAVT_wX_=J+Dh0-AEdKPdVMbkSzW3Q@mail.gmail.com> (Frederic Tessier's message of "Wed, 19 Jan 2022 12:51:34 -0500")

Frederic Tessier <ftessier@gmail.com> writes:

> What did you expect to happen? (Expected behavior)
> New repo initialized containing no copyright claims
>
> What happened instead? (Actual behavior)
> New repo initialized with a copyright claim in .git/hooks/pre-rebase.sample:
> # Copyright (c) 2006, 2008 Junio C Hamano

Because the sample files are copied verbatim, with or without such
copyright notice message, they are copyrighted by their respective
copyright holders.  And their modification and distribution should
follow the same licensing terms (i.e. GPLv2) as our source files.

Removing that single line would not change anything, as these days
the written copyright notice is optional across the globe.

We could probably stop shipping these .sample hook files, or the
users can ignore them with the same ease.

I dunno.  An alternative position on the other extreme is to find
and convince all the copyright holders of template/, relicense these
files under less restrictive license _and_ state the license clearly
in each of these files.  I think that ought to be our long term
direction.

Thanks for bringing this up.

  reply	other threads:[~2022-01-19 19:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 17:51 Dangling copyright in git hook template Frederic Tessier
2022-01-19 19:49 ` Junio C Hamano [this message]
2022-01-19 21:25   ` Frederic Tessier

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=xmqqbl07mrp3.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ftessier@gmail.com \
    --cc=git@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 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).