From: Danny Siu <dsiu@adobe.com>
Subject: Re: Making Gcc messages automatically dormant
Date: Tue, 16 Sep 2003 17:52:20 -0700 [thread overview]
Message-ID: <un0d4uth7.fsf@adobe.com> (raw)
In-Reply-To: <"m34qzq90dg.fsf_-nf--_xmat_-m:gnus_---"@tuxie.homelinux.net>
I am in the same situation where i always gcc email I write to the group I
post to for archiving purpose and for the thread completeness. Right now I
have to manually mark them as dormant.
gnus-gcc-mark-as-[dormant, ticked] would be nice to have.
Nelson Ferreira writes:
njsf> Hi all,
njsf> I use (setq gnus-gcc-mark-as-read t)
njsf> Is there a gnus-gcc-mark-as-dormat ? To me it makes a lot more
njsf> sense when I followup in email groups with expiration. This way I
njsf> will never loose my own emails :)
njsf> Thanks,
njsf> Nelson
njsf> -- Nelson Ferreira
--
Danny Dick-Fung Siu mailto:dsiu@adobe.com
Advanced Technology Group @ Adobe Systems Incorporated
next parent reply other threads:[~2003-09-17 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <"m34qzq90dg.fsf_-nf--_xmat_-m:gnus_---"@tuxie.homelinux.net>
2003-09-17 0:52 ` Danny Siu [this message]
2003-10-17 17:57 ` Lars Magne Ingebrigtsen
2003-10-17 22:45 ` Nelson Ferreira
2003-09-06 1:22 Nelson Ferreira
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=un0d4uth7.fsf@adobe.com \
--to=dsiu@adobe.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 NNTP newsgroup(s).