From: Luke Davis <ldavis@dynanet.com>
To: blinux-list@redhat.com
Subject: Re: to much list info
Date: Mon, 9 Dec 1996 13:09:51 -0500 (EST) [thread overview]
Message-ID: <Pine.BSI.3.95.961209130746.11158M-100000@hyperion.dynanet.com> (raw)
In-Reply-To: <199612091749.JAA15130@eos.arc.nasa.gov>
I agree with Jim here; it adds alot of unnecessary date to messages that
are saved.
It's fine once; but when you save as much as I do, it really adds up . .
.
If it is necessary to have this; why just not send a refresher message,
once a montu, or something?
On Mon, 9 Dec 1996, Jim Stevenson wrote:
> Hi.
>
> I save many of the list messages to get a base of helpful data for when I
> transission to lynnex.
>
> Could we illiminate the subscription and unsubscribe from the end of each message?
>
> Those who are on the list should already know this, so repeating it just
> wastes disk space.
>
> Thanks much
>
> ---
> Send your message for blinux-list to blinux-list@redhat.com
> Blinux software archive at ftp://leb.net/pub/blinux
> Blinux web page at http://leb.net/blinux
> To unsubscribe send mail to blinux-list-request@redhat.com
> with subject line: unsubscribe
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Jim Stevenson
` Luke Davis [this message]
` John Schucker
` Hans Zoebelein
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=Pine.BSI.3.95.961209130746.11158M-100000@hyperion.dynanet.com \
--to=ldavis@dynanet.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).