From: Jody <jbruchon@nc.rr.com>
To: Eddy <eddyx89@users.sourceforge.net>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Elks
Date: Tue, 08 Aug 2006 18:38:55 -0400 [thread overview]
Message-ID: <44D9127F.5010805@nc.rr.com> (raw)
In-Reply-To: <E1GAaBy-0003ur-UX@sc8-sf-web1.sourceforge.net>
You need to submit some potential patches to the ELKS mailing list,
linux-8086@vger.kernel.org first. If you submit quality patches, you
can become eligible to be promoted to developer status.
Jody
Eddy wrote:
> Message body follows:
>
> I would like to contribute to elks project by becoming a
> developer, how can I do this? thanks.
>
> --
> This message has been sent to you, a registered SourceForge.net user,
> by another site user, through the SourceForge.net site. This message
> has been delivered to your SourceForge.net mail alias. You may reply
> to this message using the "Reply" feature of your email client, or
> using the messaging facility of SourceForge.net at:
> https://sourceforge.net/sendmessage.php?touser=1570603
>
next parent reply other threads:[~2006-08-08 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1GAaBy-0003ur-UX@sc8-sf-web1.sourceforge.net>
2006-08-08 22:38 ` Jody [this message]
2007-08-08 9:30 elks Andrew V. Suvorow
2007-08-08 10:05 ` elks Alan Cox
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=44D9127F.5010805@nc.rr.com \
--to=jbruchon@nc.rr.com \
--cc=eddyx89@users.sourceforge.net \
--cc=linux-8086@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.