From: "Maciej Sołtysiak" <pysiak.satriani@wp.pl>
To: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Looking for Kernel hacking or storage systems design and code consulting work
Date: Wed, 23 Aug 2006 10:46:39 +0200 [thread overview]
Message-ID: <838067156.20060823104639@wp.pl> (raw)
In-Reply-To: <44EC0F6F.3020100@namesys.com>
Hello Hans,
Wednesday, August 23, 2006, 10:18:55 AM, you wrote:
> We have a complete team of kernel programmers available. Do you have
> race conditions you need found, spaghetti code from a predecessor that
> nobody can do anything with, a driver you want made to work, or a
> storage related feature you need? We can do it. Our guys are quite
> senior, and we have been doing Linux filesystem programming since 1993.
> Would you like an outsider to review a design, or someone for a
> technical advisory board? We can do it.
If that gets to lwn.net, kerneltrap.org, slashdot.org, osnews.com, etc...
that might help also.
I will try to write a quick news to 2 well known linux portals in my country
too. Hope that helps.
--
Best regards,
Maciej
prev parent reply other threads:[~2006-08-23 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 8:18 Looking for Kernel hacking or storage systems design and code consulting work Hans Reiser
2006-08-23 8:46 ` Maciej Sołtysiak [this message]
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=838067156.20060823104639@wp.pl \
--to=pysiak.satriani@wp.pl \
--cc=reiserfs-list@namesys.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 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.