From: "Thomas König" <tk@tkoenig.net>
Cc: overseers@gcc.gnu.org, gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments))
Date: Mon, 9 Mar 2020 20:49:45 +0100 [thread overview]
Message-ID: <187b444a-df65-7bb2-1a18-c4b9ecdc2d43@tkoenig.net> (raw)
In-Reply-To: <20200309102520.GQ2156@tucnak>
Hi,
Some comments.
Generally, I found the old format to be very good for navigating, and I
would like to have the new one match the old one as closely as possible.
> 1) the by date monthly list of mails used to be ordered newest to oldest
> mails first, now it is oldest to newest, so when dealing with new stuff one
> has to always scroll dow
Also important if one just wants to search; it is often the newest
(or newer) message that is of interest.
> 2) the dates and times of mails used to be shown (date as a section in the
> list, times in the left column), now there is nothing, so without clicking
> something it is hard to guess how exactly old it is
I concur, that is irritating. You can guess, but you don't get the same
sort of what's happening just from a glance.
> 3) the columns were nicer (date, subject left justified, email right
> justified, now there are no columns)
This does make it harder to see what's what, true.
> 4) some headers were shown, now there is nothing
Yep.
> 5) emails used to be sanitized against harvesters, now they aren't
Surely, there is a feature for this?
> 6) there used to be a Raw text URL to grab the raw email, now there is nothing
This is something that I have rarely used.
As far as the advantages go: A per-thread view is nice, but I don't
think having it outweighs the disadvantages above.
From my personal preference, having 1), 2) and 3) (basically, let the
new interface look like the old one) would be great.
Regards
Thomas
next prev parent reply other threads:[~2020-03-09 19:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C92C61E7-EF8A-4AD7-904D-FA6E0AD6649C@tkoenig.net>
2020-03-09 8:40 ` gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments) Tobias Burnus
2020-03-09 8:48 ` Thomas König
2020-03-09 9:46 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments)) Tobias Burnus
2020-03-09 9:51 ` List-Id header being stripped (was:Re: Mailing list stripping off attachments) Richard Bradfield
2020-03-09 10:27 ` List-Id header being stripped Andreas Schwab
2020-03-09 10:44 ` Richard Bradfield
2020-03-09 10:30 ` Florian Weimer
2020-03-09 10:49 ` Richard Earnshaw
2020-03-09 11:32 ` Florian Weimer
2020-03-09 12:28 ` Gerald Pfeifer
2020-03-09 10:25 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments)) Jakub Jelinek
2020-03-09 10:47 ` Jonathan Wakely
2020-03-09 11:21 ` text/x-* attachments stripped Andreas Schwab
2020-03-09 13:57 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments)) Thomas König
2020-03-09 15:45 ` text/x-* attachments strippe Gerald Pfeifer
2020-03-09 16:03 ` Frank Ch. Eigler
2020-03-09 16:53 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline Nathan Sidwell
2020-03-09 17:06 ` Andreas Schwab
2020-03-09 17:07 ` Jonathan Wakely
2020-03-09 17:20 ` text/x-* attachments stripped Nathan Sidwell
2020-03-09 19:49 ` Thomas König [this message]
2020-03-09 22:11 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments)) Jonathan Wakely
2020-03-09 21:07 ` Joseph Myers
2020-03-09 23:16 ` Jonathan Wakely
2020-04-03 14:29 ` Martin Liška
2020-04-03 15:19 ` Christopher Faylor
2020-04-03 15:43 ` mailman customization Martin Liška
2020-04-03 15:54 ` Frank Ch. Eigler
2020-04-03 15:58 ` Martin Liška
2020-04-03 16:30 ` Christopher Faylor
2020-04-03 16:42 ` Christopher Faylor
2020-04-03 20:52 ` mailman customization not quite right yet Christopher Faylor
2020-04-04 9:20 ` Martin Liška
2020-05-05 9:57 ` Martin Liška
2020-05-05 14:23 ` Christopher Faylor
2020-04-03 16:36 ` mailman customization Christopher Faylor
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=187b444a-df65-7bb2-1a18-c4b9ecdc2d43@tkoenig.net \
--to=tk@tkoenig.net \
--cc=gcc@gcc.gnu.org \
--cc=overseers@gcc.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 read-only IMAP folder(s) and NNTP newsgroup(s).