From: Michael Shmulevich <michaels@jungo.com>
To: "uclibc@opensource.lineo.com" <uclibc@opensource.lineo.com>,
"busybox@opensource.lineo.com" <busybox@opensource.lineo.com>,
Linux/MIPS <linux-mips@oss.sgi.com>
Subject: Double-posting
Date: Thu, 26 Apr 2001 20:11:10 +0200 [thread overview]
Message-ID: <3AE864BD.4106010A@jungo.com> (raw)
Hello all,
I apologise before the audience for double-posting of my last several
messages.
My mail server seemingly confused me, saying that during last few hours
the mail was not sent.
I blindly re-posted messages, and later on accepted a confirmation about
my previous posting.
Sorry again,
Michael.
reply other threads:[~2001-04-26 17:06 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=3AE864BD.4106010A@jungo.com \
--to=michaels@jungo.com \
--cc=busybox@opensource.lineo.com \
--cc=linux-mips@oss.sgi.com \
--cc=uclibc@opensource.lineo.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