From: Sean Neakums <sneakums@zork.net>
Subject: Re: Feature Req: set vacation for mailing lists in bulk
Date: Sat, 13 Apr 2002 19:52:02 +0100 [thread overview]
Message-ID: <6uy9frtorx.fsf@zork.zork.net> (raw)
In-Reply-To: <87n0w7obe7.fsf@cs.utah.edu> (Karra's message of "Sat, 13 Apr 2002 21:10:00 +0530")
commence Karra quotation:
> How do people handle the problem of setting vacation flags for tens of
> mailinglists in a sensible and easy manner.
I don't. Sending at most one automatic vacation message in response
to private mail is fine, but mailing lists do not need to be cluttered
up with worthless "I am on vacation, if you need anything, please
contact Sheila across the hall or John in Accounting" messages. If
the people on certain mailing lists *need* to know you are on
vacation, please take five minutes and write them a personal note.
They will appreciate it.
--
///////////////// | | The spark of a pin
<sneakums@zork.net> | (require 'gnu) | dropping, falling feather-like.
\\\\\\\\\\\\\\\\\ | | There is too much noise.
next prev parent reply other threads:[~2002-04-13 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-13 15:40 Karra
2002-04-13 18:52 ` Sean Neakums [this message]
2002-04-13 20:23 ` Russ Allbery
2002-04-13 20:44 ` Sean Neakums
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=6uy9frtorx.fsf@zork.zork.net \
--to=sneakums@zork.net \
/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).