From: Frederic Tessier <ftessier@gmail.com>
To: git@vger.kernel.org
Subject: Dangling copyright in git hook template
Date: Wed, 19 Jan 2022 12:51:34 -0500 [thread overview]
Message-ID: <CAB7QKarvGGjNf-bvuKqwnAVT_wX_=J+Dh0-AEdKPdVMbkSzW3Q@mail.gmail.com> (raw)
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
git init
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
What's different between what you expected and what actually happened?
There is a file in the fresh repo (copied from the template file
git-core/templates/hooks/pre-rebase.sample) which contains a copyright
statement, moreover without any licence to use the file.
Anything else you want to add:
This also happens upon running the 'git clone' command. This is an issue
because when users clone a project, they are left with a copyrighted dependency
(without any licence), even though the repository itself did not contain that
file. This occurs tacitly, and users would be unknowingly violating the
copyright if they happened to further convey the file.
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.34.1
[Enabled Hooks]
next reply other threads:[~2022-01-19 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 17:51 Frederic Tessier [this message]
2022-01-19 19:49 ` Dangling copyright in git hook template Junio C Hamano
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
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='CAB7QKarvGGjNf-bvuKqwnAVT_wX_=J+Dh0-AEdKPdVMbkSzW3Q@mail.gmail.com' \
--to=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.
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).