From: Konstantin Boldyshev <konst@linuxassembly.org>
To: "linux-assembly@vger.kernel.org" <linux-assembly@vger.kernel.org>
Subject: linux assembly stuff for sale :)
Date: Mon, 12 Feb 2007 21:17:29 +0300 [thread overview]
Message-ID: <45D0AF39.5090306@linuxassembly.org> (raw)
Everyone,
From now on, linuxassembly.org is looking for a new maintainer.
As I am now mostly in Linux kernel for last years (read C universe),
it would be great to find assembly-addicted person, who would take
the place. Site maintainer should be familiar with assembly language
and have minimal html expertise. Understanding linuxassembly.org goals
and principles, and following them is a must. Any new insight, from
complete site redesign to eventual improvement is welcome.
Linux Assembly HOWTO is seeking new maintainer as well.
Of course it could be a different person than linuxassembly.org maintainer.
Oh, well... the same applies to asmutils and a-linux.
asmutils maintainer should be familiar with asmutils as a developer.
Certainly, everything above has to be done on voluntary basis.
Feel free to contact me if you are interested.
--
Regards,
Konstantin.
reply other threads:[~2007-02-12 18:17 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=45D0AF39.5090306@linuxassembly.org \
--to=konst@linuxassembly.org \
--cc=linux-assembly@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;
as well as URLs for NNTP newsgroup(s).