From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Sorting "New features in No Gnus" by topic?
Date: Fri, 31 Mar 2006 17:06:44 +0200 [thread overview]
Message-ID: <v94q1ezm9n.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <878xqrd8wb.fsf@pacem.orebokech.com>
On Thu, Mar 30 2006, Romain Francoise wrote:
> * Installation changes in No Gnus
> * Major new features in No Gnus
> * Changes in back ends
> * Changes in Message
> * Other changes in No Gnus
>
> ... which seems to balance entries pretty nicely with the items we
> currently have. Feel free to split/reorder as you see fit.
>
> (Note that this required changes to gnus-news.el as well.)
Thank you very much for working on this. It's much better than
before.
However, the category "Major new features" implies that these features
are more important than others[1], e.g. those from "Other changes".
I'd rather use purely topical categories.
I will try to categorize the entries from "Major new features" and
"Other changes" into the existing or new categories, e.g. "Reading
messages" (summary and article buffer) and "General/other" (tool bar,
new packages, ...).
(It seem you lost "The tool bar has been updated to use GNOME icons.",
I will restore it.)
Bye, Reiner.
[1] I didn't even use half of the "Major" items yet whereas some
"Other changes" improve Gnus a lot for me.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-03-31 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 21:01 Reiner Steib
2006-03-30 19:34 ` Romain Francoise
2006-03-31 15:06 ` Reiner Steib [this message]
2006-03-31 16:17 ` Romain Francoise
2006-03-31 17:07 ` Reiner Steib
2006-03-31 17:26 ` Romain Francoise
2006-03-31 17:49 ` Reiner Steib
2006-03-31 20:58 ` Sorting "New features in Oort Gnus" by topic? (was: Sorting "New features in No Gnus" by topic?) Reiner Steib
2006-05-12 14:59 ` Sorting "New features in Oort Gnus" by topic? Reiner Steib
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=v94q1ezm9n.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).