From: Eric Kimminau <eak@detroit.sgi.com>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: Moving drivers/sgi around
Date: Tue, 09 Feb 1999 07:09:55 -0800 [thread overview]
Message-ID: <36C04FC3.D7120153@detroit.sgi.com> (raw)
In-Reply-To: Pine.LNX.3.96.990208190349.11444F-100000@lager.engsoc.carleton.ca
Alex deVries wrote:
>
> Are there any objections to me moving drivers/sgi and merging them into
> the 'correct' places? The places in question are:
>
> newport and colsole stuff: drivers/video
> hal: drivers/sound
> vino: drivers/char (which is there, actually)
>
> Any objections?
>
> - Alex
Sounds like the right thing to do to me.
--
---------1---------2---------3---------4---------5---------6---------7
Eric Kimminau eak@sgi.com Electronic Support Tools
Vox:248-848-4455 Fax:248-848-5600 VNET:6-327-4455
"I speak my mind and no one else's."
"I am a bomb technician. If you see me running, try to keep up..."
http://support.sgi.com
next prev parent reply other threads:[~1999-02-09 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-09 0:06 Moving drivers/sgi around Alex deVries
1999-02-09 15:09 ` Eric Kimminau [this message]
1999-02-09 21:31 ` Thomas Bogendoerfer
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=36C04FC3.D7120153@detroit.sgi.com \
--to=eak@detroit.sgi.com \
--cc=adevries@engsoc.carleton.ca \
--cc=eak@sgi.com \
--cc=linux@cthulhu.engr.sgi.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