From: Daniel Brockman <daniel@brockman.se>
To: info-gnus-english@gnu.org
Subject: Re: Process mark use cases
Date: Sat, 10 Feb 2007 07:43:31 +0100 [thread overview]
Message-ID: <877iuqh5rg.fsf@wigwam.brockman.se> (raw)
In-Reply-To: <m2veibxp2b.fsf@cyberhut.org>
CHENG Gao <chenggao@gmail.com> writes:
> I like to put NGs under topics. For example, I may open gmane and
> subscribe to many groups at one time, and I mark all Emacs related
> groups (like Bongo ;-p),
Hey! :-)
> and T m emacs RET
I see.
> For emails, I dont do split while receiving them. I keep them in inbox
> thus I wont forget to reply them when I have time. And after some time,
> when things settled, I move them to specific groups for archiving. I use
> structure like:
> biz.some-company
> prv.some-person
>
> So I frequently do mark, B m
Okay. Yes, moving seems like a popular use case.
> Mostly for these two purposes.
Thanks.
--
Daniel Brockman <daniel@brockman.se>
next prev parent reply other threads:[~2007-02-10 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4233.1171035615.2155.info-gnus-english@gnu.org>
2007-02-09 16:25 ` David Z Maze
2007-02-10 6:40 ` Daniel Brockman
2007-02-09 16:39 ` CHENG Gao
2007-02-10 6:43 ` Daniel Brockman [this message]
2007-02-09 15:24 Daniel Brockman
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=877iuqh5rg.fsf@wigwam.brockman.se \
--to=daniel@brockman.se \
--cc=info-gnus-english@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 NNTP newsgroup(s).