From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, nico@cam.org
Cc: art.08.09@gmail.com, bdonlan@gmail.com, git@vger.kernel.org,
johnflux@gmail.com, P@draigBrady.com,
torvalds@linux-foundation.org
Subject: Re: Linus' sha1 is much faster!
Date: 17 Aug 2009 19:12:08 -0400 [thread overview]
Message-ID: <20090817231208.32039.qmail@science.horizon.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0908171513230.6044@xanadu.home>
>> The purpose of the rewrite is to avoid having to make
>> pessimistic assumptions about people who don't respond.
>>
>> I suppose I should have made that request clearer:
>> Is there anyone who claims copyright on anything here?
>> Or would just like credit?
>> If so, are you willing to donate it to the public domain?
> I think this is much nicer to everyone involved.
>
> As far as I'm concerned, I'm OK with giving any small copyright I might
> have in this SHA1 implementation, if any, to the public domain.
> Credits are always nice.
My apologies. I read a lot of people talking about wanting the code
under different licenses, and thought I'd just cut through it by
providing some PD code.
I didn't turn around and look at it from the point of view of the
people who'd put the work into developing it. I don't mean to deny
anyone credit for their work. In fact, providing more detail is on
the to-do list, but I haven't waded through the mail archives and
tracked down who contributed what yet.
I'll work on those polish details once I have it producing the same
assembly code as Linus'.
There are a lot of possible highly-permissive licenses if one is wanted
(zlib, MIT, CC-by), but public domain seems simpler.
next prev parent reply other threads:[~2009-08-17 23:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 7:23 Linus' sha1 is much faster! George Spelvin
2009-08-17 14:20 ` Nicolas Pitre
2009-08-17 17:06 ` Nicolas Pitre
2009-08-17 17:20 ` Paolo Bonzini
2009-08-17 18:54 ` George Spelvin
2009-08-17 19:34 ` Nicolas Pitre
2009-08-17 23:12 ` George Spelvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-14 23:25 Pádraig Brady
2009-08-15 20:02 ` Bryan Donlan
2009-08-15 20:12 ` John Tapsell
2009-08-15 20:23 ` Linus Torvalds
2009-08-15 20:54 ` Linus Torvalds
2009-08-17 1:55 ` Nicolas Pitre
2009-08-26 11:39 ` Pádraig Brady
2017-04-20 21:35 ` galt
2017-04-20 21:38 ` galt
2009-08-17 8:22 ` Andreas Ericsson
2009-08-16 0:06 ` Theodore Tso
2009-08-16 19:25 ` Giuseppe Scrivano
2009-08-16 20:10 ` Linus Torvalds
2009-08-16 22:15 ` Giuseppe Scrivano
2009-08-16 22:47 ` Linus Torvalds
2009-08-17 1:53 ` Pádraig Brady
2009-08-17 10:51 ` Giuseppe Scrivano
2009-08-17 15:44 ` Steven Noonan
2009-08-17 16:22 ` Linus Torvalds
2009-08-17 21:43 ` Steven Noonan
2009-08-17 17:32 ` Giuseppe Scrivano
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=20090817231208.32039.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=P@draigBrady.com \
--cc=art.08.09@gmail.com \
--cc=bdonlan@gmail.com \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
--cc=nico@cam.org \
--cc=torvalds@linux-foundation.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).