From: Philip Vossler <philvossler@googlemail.com>
To: dm-devel@redhat.com
Subject: OT: device mapper development/testing.
Date: Fri, 10 Sep 2010 20:04:40 +0100 [thread overview]
Message-ID: <AANLkTi=1ZTOodvDAnF4FNR0+GAv2rTGhpnB-+99H5afC@mail.gmail.com> (raw)
Is there any way I can assist in the development of device mapper
(particularly dmraid)? I have limited programming skills - I am a Test
Engineer primarily involved with hardware working for a small computer
company that manufactures a variety of systems.
I have used and supported the use of Linux for some time. I have
access to a wide range of hardware mostly based on Intel cpu's and
chipsets.
If there is anyway I can contribute by testing software on a variety
of hardware please email me off list. I would very much like to put
something back into Linux as I have benefited in so many ways from
it's availability.
(I only wish I had the time to furher develop my limited programming
skills in order to be of greater use to the community)
Sincerely
Phil Vossler
--
"of all the paths you choose in life,
make sure some of them are dirt..."
reply other threads:[~2010-09-10 19:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='AANLkTi=1ZTOodvDAnF4FNR0+GAv2rTGhpnB-+99H5afC@mail.gmail.com' \
--to=philvossler@googlemail.com \
--cc=dm-devel@redhat.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;
as well as URLs for NNTP newsgroup(s).