From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: List outage
Date: Tue, 08 Sep 2009 22:10:00 -0400 [thread overview]
Message-ID: <4AA70E78.10109@balister.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 159 bytes --]
Sorry about the list outage. The linuxtogo server moved and I forgot
that machine handles the oe list email. Things should be back to normal now.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next reply other threads:[~2009-09-09 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 2:10 Philip Balister [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-15 14:31 List outage Mads Martin Joergensen
2005-07-18 13:17 ` Mads Martin Joergensen
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=4AA70E78.10109@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.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.