From: "Jeremy W. Murphy" <jwm@amc.com.au>
To: gcc-help@gnu.org
Subject: Annoying away messages.
Date: Sun, 31 Oct 1999 13:57:00 -0000 [thread overview]
Message-ID: <3.0.32.19991004110512.006d8604@mail.amc.localnet> (raw)
Message-ID: <19991031135700.MDpVVyuKDdxNP9_gKDEnJ8B3TFixdW_yJaYZKLLxmj8@z> (raw)
>Return-Path: <AWAY$SERVER@spf.fairchildsemi.com>
>Delivered-To: jwm@amc.com.au
>From: AWAY$SERVER@spf.fairchildsemi.com
>Date: Sun, 03 Oct 1999 20:48:38 -0400 (EDT)
>Subject: Away notice for DFLETCHE [Re: RE: GCC-2.95.1 on SGI O2]
>To: jwm@amc.com.au
>X-VMS-To: SMTP%"jwm@amc.com.au"
>
>Automatic Away Notice for DFLETCHE.
>
>I am out of the office at this time,
>and will answer your email when I return.
>Please contact Dana Hodgkins for any issues in my absense.
>Thank you,
>-David
This is the second one of these messages that I have received after
replying to a message in this list -- they are starting to bug me!
Who/what is sending them? 'Cause I don't remember any Dana Hodgkins or
David in the messages I replied to.
Jeremy
next reply other threads:[~1999-10-31 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-03 18:04 Jeremy W. Murphy [this message]
1999-10-31 13:57 ` Jeremy W. Murphy
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=3.0.32.19991004110512.006d8604@mail.amc.localnet \
--to=jwm@amc.com.au \
--cc=gcc-help@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).