From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: nnima-split-with-parent
Date: Sat, 07 Dec 2002 16:28:34 +0100 [thread overview]
Message-ID: <848yz1rgpp.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3lm31g8ti.fsf@heechee.beld.net> (Ted Zlatanov's message of "Sat, 07 Dec 2002 10:14:33 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> Storing things as "backend\tmessage-id\tgroupname" is easier to parse
> (since we always want to separate the backend from the groupname), and
> the field order makes it easier to reuse the old nnmail-cache
> functions. That's why I suggested that format. I'm OK with any other format.
gnus-group-name-to-method can convert a fully qualified group name
into a method, and gnus-group-real-name gets the group name without
server.
So we're back to the `matter of taste' thing :-p
But this doesn't deal with the unqualified group names that are
currently in the file.
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-12-07 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 20:24 nnima-split-with-parent Ted Zlatanov
2002-12-07 14:59 ` nnima-split-with-parent Kai Großjohann
2002-12-07 18:20 ` nnima-split-with-parent Ted Zlatanov
2002-12-07 20:22 ` nnima-split-with-parent Kai Großjohann
[not found] ` <m2k7imroo1.fsf@tnuctip.rychter.com>
2002-12-07 13:54 ` nnimap-split-with-parent Ted Zlatanov
2002-12-07 15:01 ` nnima-split-with-parent Kai Großjohann
2002-12-07 15:14 ` nnima-split-with-parent Ted Zlatanov
2002-12-07 15:28 ` Kai Großjohann [this message]
2002-12-07 18:20 ` nnima-split-with-parent Ted Zlatanov
2002-12-07 20:25 ` nnima-split-with-parent Kai Großjohann
2002-12-09 15:54 ` nnima-split-with-parent Ted Zlatanov
2002-12-09 16:21 ` nnima-split-with-parent Kai Großjohann
[not found] ` <m27kelycce.fsf@tnuctip.rychter.com>
2002-12-07 20:23 ` nnima-split-with-parent Kai Großjohann
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=848yz1rgpp.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.de \
--cc=ding@gnus.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).