From: Jeremy White <jwhite@codeweavers.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: isofs unhide option: troubles with Wine
Date: 03 Jun 2002 12:05:57 -0500 [thread overview]
Message-ID: <1023123957.8071.140.camel@jwhite> (raw)
In-Reply-To: <1022341822.11859.36.camel@irongate.swansea.linux.org.uk>
> possible rather than impossible. Question is - why was hide the default
> and what was that decision based upon ?
I agree with Alan - this is the key question.
I would further argue that silence in response to this question
suggests that there was no carefully considered reason;
presumably a good hacker just followed the spec, without considering how
these CDs are actually used.
It further suggests to me that I should prep a patch.
Thoughts? Screams of protest? Helpful tips on to whom I
should send the patch?
Thanks,
Jer
next prev parent reply other threads:[~2002-06-03 17:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-25 4:30 isofs unhide option: troubles with Wine Jeremy White
2002-05-25 13:46 ` Olaf Dietsche
2002-05-25 13:49 ` Jeremy White
2002-05-25 14:01 ` Joseph Mathewson
2002-05-25 14:23 ` Jeremy White
2002-06-10 3:12 ` Francois Gouget
2002-06-10 11:52 ` Thunder from the hill
2002-06-10 12:38 ` Guest section DW
2002-05-25 15:50 ` Alan Cox
2002-06-03 17:05 ` Jeremy White [this message]
2002-06-03 18:06 ` Thunder from the hill
2002-06-03 18:40 ` H. Peter Anvin
2002-06-03 19:40 ` Thunder from the hill
2002-06-03 19:43 ` H. Peter Anvin
2002-06-04 0:23 ` Alan Cox
2002-06-19 2:36 ` Jeremy White
2002-05-25 14:18 ` Ruth Ivimey-Cook
2002-05-25 14:25 ` Jeremy White
2002-05-25 19:31 ` H. Peter Anvin
2002-05-25 19:40 ` Linus Torvalds
2002-05-25 20:31 ` H. Peter Anvin
2002-05-25 21:20 ` Lionel Bouton
2002-05-25 21:51 ` H. Peter Anvin
2002-05-25 21:07 ` Lionel Bouton
-- strict thread matches above, loose matches on Subject: below --
2002-05-25 17:04 Andries.Brouwer
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=1023123957.8071.140.camel@jwhite \
--to=jwhite@codeweavers.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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.
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.