From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: [rgnus] FCC in message-mode to nnml group?
Date: 07 Jan 1997 21:25:10 +0100 [thread overview]
Message-ID: <m268192py1.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Mark Borges's message of 07 Jan 1997 13:08:01 -0700
Mark Borges <mdb@cdc.noaa.gov> writes:
> Would/could it work? If so, what would the semantics be? (the message
> would need to be filed to a dynamic numeric filename I suppose). I'd
> like the reply that I save to be filed in the *same* nnml folder, for
> threading purposes.
>
> Or does everyone just bag FCC: use and instead opt for BCC: or CC:?
People use Gcc instead. See the manual for details.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1997-01-07 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-07 20:08 Mark Borges
1997-01-07 20:25 ` Lars Magne Ingebrigtsen [this message]
1997-01-07 20:55 ` Lars Balker Rasmussen
1997-01-07 22:58 ` Steven L Baur
1997-01-08 0:49 ` Mark Borges
1997-01-08 2:11 ` David Moore
1997-01-08 3:45 ` Sudish Joseph
1997-01-08 7:40 ` Jens Lautenbacher
1997-01-08 17:15 ` David Moore
1997-01-09 7:49 ` Jens Lautenbacher
1997-01-07 21:23 ` David S. Goldberg
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=m268192py1.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).