From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [patch] gdb/CONTRIBUTE update
Date: Tue, 26 Feb 2013 13:12:00 -0000 [thread overview]
Message-ID: <20130226131213.GA15184@host2.jankratochvil.net> (raw)
In-Reply-To: <512C9996.6000007@redhat.com>
On Tue, 26 Feb 2013 12:16:38 +0100, Pedro Alves wrote:
> On 02/26/2013 09:38 AM, Jan Kratochvil wrote:
> > With a reply mail users (reviewers) which use sorting of mail folder by
> > threads (in Mutt 'o' 't') get the PING mail put under the original mail which
> > is far in the past and the PING mail gets hidden+forgotten again due to it.
> >
> > This even is not an idea of mine, it was concluded on some GNU Tools Cauldron.
>
> Do you like it? I don't.
I do.
> Interesting. I had seen some pings like that on the gcc list, but I never
> understood why people preferred them that way.
The discussion at Cauldron was primarily for GCC.
> I'm currently using Thunderbird, and it sorts threads by most recent reply,
> not by original post date
I do not see such option in Mutt. Mutt could be sure extended but as I can
imagine it is also not perfect as old but still discussed threads clutter new
posts. Besides that there are other mailers like VM/Gnus which also may not
have thre thread-by-most-recent-reply sorting, not sure.
> A separate email with an url means more work for me, as I then have to go
> look up the thread in Thunderbird that corresponds to that url,
This is why I started to include also Message-IDs besides the URLs. Posting
just the Message-IDs is unfortunately insufficient.
Looking up the URL from mailer/Mutt is also a pain, I wanted to code some
script for Message-ID -> URL mapping but as sourceware server should be
replaced ASAP which will replace MHonArc by PiperMail I have not yet coded it;
unfortunately the ASAP replace takes already some years.
Unfortunately whatever method we find out it always is a pain, the reviewing
process should be supported by projects like Gerrit. Until that is
tried/established the goal is just to find the least pain.
Jan
next prev parent reply other threads:[~2013-02-26 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 20:26 Jan Kratochvil
2013-02-21 21:01 ` Tom Tromey
2013-02-26 9:32 ` Yao Qi
2013-02-26 9:38 ` Jan Kratochvil
2013-02-26 9:52 ` Yao Qi
2013-02-26 13:16 ` Jan Kratochvil
2013-02-26 11:16 ` Pedro Alves
2013-02-26 13:12 ` Jan Kratochvil [this message]
2013-02-28 20:01 ` Tom Tromey
[not found] ` <20130228212725.GA1848@host2.jankratochvil.net>
2013-03-01 16:27 ` Tom Tromey
2013-03-01 16:41 ` Jan Kratochvil
2013-03-01 16:51 ` Tom Tromey
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=20130226131213.GA15184@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=yao@codesourcery.com \
/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