From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Muli Ben-Yehuda <muli@il.ibm.com>,
Jonathan Day <imipak@yahoo.com>,
linux-kernel@vger.kernel.org, Zvika Gutterman <zvi@safend.com>
Subject: Re: /dev/random on Linux
Date: Tue, 16 May 2006 11:24:04 +0100 [thread overview]
Message-ID: <1147775045.2151.12.camel@localhost.localdomain> (raw)
In-Reply-To: <B2E79864-3AC6-4B72-B97B-222FEDA136A1@mac.com>
On Maw, 2006-05-16 at 04:15 -0400, Kyle Moffett wrote:
> > Zvi did contact Matt Mackall, the current /dev/random maintainer,
> > and was very keen on discussing the paper with him. I don't think
> > he got any response.
>
> So he's demanding that one person spend time responding to his
> paper?
Relying on email to one person getting through is a bit bogus, but I
don't see a single demand from anyone that someone respond to the paper.
I'm very glad the work was done, it would have been nicer to have known
up front but it didn't work out.
Also if the maintainer doesn't respond and the paper authors didn't know
where to go next that in itself needs addressing because the same may be
true for others finding problems.
Don't blame the messenger when it might be useful to think about whether
the MAINTAINERS file could do with an extra paragraph or two...
Alan
next prev parent reply other threads:[~2006-05-16 10:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 21:39 /dev/random on Linux Jonathan Day
2006-05-15 22:41 ` Alan Cox
2006-05-16 2:50 ` Muli Ben-Yehuda
2006-05-16 8:15 ` Kyle Moffett
2006-05-16 8:28 ` Muli Ben-Yehuda
2006-05-16 8:52 ` Kyle Moffett
2006-05-16 13:54 ` Zvi Gutterman
2006-05-16 20:17 ` Theodore Tso
2006-05-16 20:37 ` Chase Venters
2006-05-17 21:32 ` Theodore Tso
2006-05-16 10:24 ` Alan Cox [this message]
2006-05-16 12:46 ` Pavel Machek
2006-05-16 15:04 ` Christopher Friesen
2006-05-16 14:58 ` Michael Buesch
2006-05-16 15:08 ` Johannes Berg
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=1147775045.2151.12.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=imipak@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=muli@il.ibm.com \
--cc=zvi@safend.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox