From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Leo Famulari <leo@famulari.name>
Cc: Guix-devel@gnu.org
Subject: Re: [PATCH] Add khmer.
Date: Mon, 27 Jun 2016 08:48:14 +1000 [thread overview]
Message-ID: <976C514C-6D4F-425F-8849-2C0C6C65C038@uq.edu.au> (raw)
In-Reply-To: <20160626173442.GA5036@jasmine>
On 27 June 2016 3:34:42 AM AEST, Leo Famulari <leo@famulari.name> wrote:
>On Sun, Jun 26, 2016 at 09:59:51PM +1000, Ben Woodcroft wrote:
>> I'm not convinced, I'm afraid. According to the SMHasher README [0]:
>>
>> >This is the home for the MurmurHash
>> <https://github.com/aappleby/smhasher/tree/master/src> family of hash
>> functions along with the SMHasher
>> <https://github.com/aappleby/smhasher/tree/master/src> test suite
>used to
>> verify them.
>>
>> So that would count that as an independent upstream distribution of
>> murmurhash, right?
>
>My understanding is that SMHasher does not create a library, but just
>provides raw source code, leaving it up to 3rd party software authors
>to
>integrate it into their applications. Is that right?
Yes. I don't see how that matters though, it is still bundling which should be avoided if possible right? What am I missing?
Ta, ben
next prev parent reply other threads:[~2016-06-26 23:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 1:23 [PATCH] Add khmer Ben Woodcroft
2016-06-17 1:23 ` [PATCH 1/3] gnu: Add python-screed Ben Woodcroft
2016-06-17 2:07 ` Leo Famulari
2016-06-17 22:57 ` Ben Woodcroft
2016-06-17 1:23 ` [PATCH 2/3] gnu: Add murmur-hash Ben Woodcroft
2016-06-17 1:23 ` [PATCH 3/3] gnu: Add khmer Ben Woodcroft
2016-06-17 7:23 ` Leo Famulari
2016-06-17 23:41 ` Ben Woodcroft
2016-06-25 17:30 ` Leo Famulari
2016-06-17 8:16 ` [PATCH] " Leo Famulari
2016-06-17 9:42 ` Ben Woodcroft
2016-06-17 17:54 ` Leo Famulari
2016-06-25 17:29 ` Leo Famulari
2016-06-26 9:58 ` Ludovic Courtès
2016-06-26 11:59 ` Ben Woodcroft
2016-06-26 17:34 ` Leo Famulari
2016-06-26 22:48 ` Ben Woodcroft [this message]
2016-06-27 5:01 ` Leo Famulari
2016-06-27 5:47 ` Ben Woodcroft
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=976C514C-6D4F-425F-8849-2C0C6C65C038@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=Guix-devel@gnu.org \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.