From: JBRUCHON <jbruchon@nc.rr.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Access to the ELKS Wiki
Date: Wed, 21 Nov 2007 23:24:27 -0500 [thread overview]
Message-ID: <4745047B.6020505@nc.rr.com> (raw)
If you receive this mailing list, are not a project admin or developer on
ELKS at SourceForge, and would like to be able to edit the ELKS Wiki, please
E-mail me directly at:
jbruchon *at* nc.rr.com
Be sure to include your SF user ID. I am mailed copies of all Wiki edits
immediately upon submission, partially to keep myself up to date on the Wiki
progress, partially to see if clarification or further edits are needed, and
partially to prevent hopefully unlikely Wiki vandalism.
If you need anything from me, do not hesitate to ask. That's what I'm here
for, and despite my real-life time restrictions and demands, I will
eventually handle reasonable requests when time allows, and if I am unable
to provide enough time, I will escalate privileges of others who are not so
restricted based on the requested tasks and the proven trustworthiness of
said others.
Thanks to all of you!
Jody
reply other threads:[~2007-11-22 4:24 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=4745047B.6020505@nc.rr.com \
--to=jbruchon@nc.rr.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox