From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: Sam Reis <sam@opencanopy.dev>,
Sebastian Thiel <sebastian.thiel@icloud.com>,
Scott Chacon <schacon@gmail.com>,
Scott Chacon <scott@gitbutler.net>,
git@vger.kernel.org
Subject: Re: [PATCH 0/4] faster SHA-1 collision detection
Date: Thu, 08 Oct 2026 10:10:54 -0700 [thread overview]
Message-ID: <xmqqece015k1.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CBbtKomawqc81MPV5Ngtc9J3M1ej4enGD3ZUzWnPSfsgw@mail.gmail.com> (D. Ben Knoble's message of "Thu, 8 Oct 2026 09:25:08 -0400")
"D. Ben Knoble" <ben.knoble@gmail.com> writes:
> but I didn't see a discussion of licensing at that time. Perhaps the
> idea is that we are clear that such code carries a different license
> from Git?
We are GPL-2 only, which means we can incorporate BSD-licensed
software as long as we satisfy its license and copyright notice
requirements.
The above is not an AI-bot-supplied answer, but what one learns when
talking to copyright lawyers or reading books on software licensing.
But sometimes asking LLM gives sufficiently useful answer. I typed
"Is GPLv2 compatible with BSD?"
in the search bar of a browser, and here is the early part of what I
got, which is not too bad.
* AI summary
Yes, GPLv2 is generally compatible with modern BSD (2-clause and
3-clause) licenses, though the direction of the combination
matters.
Compatibility Details
• BSD inside GPLv2: You can include a 2-clause or 3-clause
BSD-licensed library or code snippet inside a GPLv2-licensed
project. The resulting combined work must be distributed under
the terms of the GPLv2.
• GPLv2 inside BSD: You cannot take GPLv2-licensed code and
place it into a purely BSD-licensed project. Because the GPLv2
is a strong copyleft license, it forces the entire combined
work to be covered by the GPLv2.
next prev parent reply other threads:[~2026-10-08 17:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 11:25 [PATCH 0/4] faster SHA-1 collision detection Scott Chacon
2026-09-29 11:25 ` [PATCH 1/4] sha1dc-accel: add a block loop for sha1dc's SHA1_CTX Scott Chacon
2026-10-07 12:17 ` Johannes Schindelin
2026-09-29 11:25 ` [PATCH 2/4] sha1dc-accel: vectorize the unavoidable-bitconditions check Scott Chacon
2026-10-07 12:17 ` Johannes Schindelin
2026-10-07 21:32 ` Junio C Hamano
2026-09-29 11:25 ` [PATCH 3/4] sha1dc-accel: compress with SHA-NI on x86-64 Scott Chacon
2026-09-29 11:25 ` [PATCH 4/4] sha1dc-accel: compress with the ARMv8 SHA-1 instructions Scott Chacon
2026-10-07 12:17 ` [PATCH 0/4] faster SHA-1 collision detection Johannes Schindelin
2026-10-07 17:23 ` Junio C Hamano
2026-10-07 18:13 ` Scott Chacon
2026-10-08 6:21 ` Sebastian Thiel
2026-10-08 11:20 ` Sam Reis
2026-10-08 13:25 ` D. Ben Knoble
2026-10-08 13:59 ` Sam Reis
2026-10-08 17:10 ` Junio C Hamano [this message]
2026-10-08 17:46 ` D. Ben Knoble
2026-10-08 21:03 ` Junio C Hamano
2026-10-09 20:37 ` Todd Zullinger
2026-10-10 14:10 ` D. Ben Knoble
2026-10-10 15:37 ` Todd Zullinger
2026-10-11 14:06 ` D. Ben Knoble
2026-10-09 23:41 ` Junio C Hamano
2026-10-08 15:55 ` Junio C Hamano
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=xmqqece015k1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=sam@opencanopy.dev \
--cc=schacon@gmail.com \
--cc=scott@gitbutler.net \
--cc=sebastian.thiel@icloud.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.