From: "Sander van Dijk" <a.h.vandijk@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] patch for installation in vmware
Date: Sun, 20 Jul 2008 10:11:06 +0200 [thread overview]
Message-ID: <ba0d3bc70807200111p691025b7o96287650c799140b@mail.gmail.com> (raw)
In-Reply-To: <ba0d3bc70807190848q4d54d855k98d881200fefe02c@mail.gmail.com>
On 7/19/08, Sander van Dijk <a.h.vandijk@gmail.com> wrote:
> I think it either should be off when the user explicitly requests this,
> or the question shouldn't be asked at all (for vmware).
Unless of course, this is one of those cases where "when a vmware user
says no, he really means yes".
Anyway, since I'm not a vmware user myself, I'm not comfortable
sending in a patch (as I've no way to test it), so I hope someone else
will.
Greetings, Sander.
next prev parent reply other threads:[~2008-07-20 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 20:07 Antonin Vecera
2008-07-19 7:30 ` Sander van Dijk
2008-07-19 13:50 ` Russ Cox
2008-07-19 15:48 ` Sander van Dijk
2008-07-20 8:11 ` Sander van Dijk [this message]
2008-07-20 12:55 ` Uriel
2008-07-23 9:43 ` Sander van Dijk
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=ba0d3bc70807200111p691025b7o96287650c799140b@mail.gmail.com \
--to=a.h.vandijk@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).