From: Nick Wilson <nick@explodingnet.com>
To: blinux-list@redhat.com
Subject: Getting involved
Date: Thu, 24 Jan 2002 16:29:17 +0100 [thread overview]
Message-ID: <20020124152917.GA2602@explodingnet.com> (raw)
[-- Attachment #1: msg.pgp --]
[-- Type: text/plain, Size: 740 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi List people
I recently came across blinux through a thread on the Mutt mailing list.
I was wondering if anyone might make some suggestions as to how one
might get involved in some small capacity. I'm not sure what is really out there
that I might help with or even if I /can/ offer anything of value but I
thought this might be a good place to start.
Any comments or suggestions would be appreciated.
Cheers.
- --
Nick Wilson
Tel: +45 3325 0688
Fax: +45 3325 0677
Web: www.explodingnet.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
iD8DBQE8UChNHpvrrTa6L5oRAl6wAKCx6DoUs5kZcxsdgzf9HHPUHd4a/gCeN+Vf
5sdrx3AVh5WQeWGyNwck8do=
=GOr6
-----END PGP SIGNATURE-----
next reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Nick Wilson [this message]
` dreamwvr
` Nick Wilson
` Kenny Hitt
` Nick Wilson
` Kenny Hitt
` Nick Wilson
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=20020124152917.GA2602@explodingnet.com \
--to=nick@explodingnet.com \
--cc=blinux-list@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 read-only IMAP folder(s) and NNTP newsgroup(s).