From: Kai Grossjohann <grossjohann@charly.cs.uni-dortmund.de>
Cc: ding@gnus.org
Subject: Re: "incorrect" read order
Date: 21 Mar 1998 17:13:44 +0100 [thread overview]
Message-ID: <vafu38s2f9j.fsf@ramses.ls6.uni-do> (raw)
In-Reply-To: David Hedbor's message of "20 Mar 1998 10:44:18 -0800"
>>>>> On 20 Mar 1998, David Hedbor said:
David> The thing is that all groups don't have the same level. If
David> they did, I would get them in alphabetical order, which is
David> not what I want. One example is:
Oh, you're sorting your groups. Why do you do that? Just get them in
the right order, then set all levels the same and reading will work
fine. I'm assuming that you don't get ten new groups per day so
inserting them at the right place manually shouldn't be too much work.
kai
--
Really cancel? [OK] [Cancel]
prev parent reply other threads:[~1998-03-21 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-19 20:33 David Hedbor
1998-03-20 11:28 ` Kai Grossjohann
1998-03-20 18:44 ` David Hedbor
1998-03-20 23:40 ` Justin Sheehy
1998-03-21 0:59 ` David Hedbor
1998-03-21 16:13 ` Kai Grossjohann [this message]
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=vafu38s2f9j.fsf@ramses.ls6.uni-do \
--to=grossjohann@charly.cs.uni-dortmund.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).