From: Rich Felker <dalias@libc.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/7] sh: add support for J-Core J2 processor
Date: Fri, 29 Apr 2016 00:36:46 +0000 [thread overview]
Message-ID: <20160429003646.GA21636@brightrain.aerifal.cx> (raw)
In-Reply-To: <b8864269082ee9e5dcc079865340de70711b3272.1461880061.git.dalias@libc.org>
On Thu, Apr 28, 2016 at 07:12:19PM -0500, Rob Landley wrote:
> On 03/17/2016 06:09 PM, Rich Felker wrote:
> > Signed-off-by: Rich Felker <dalias@libc.org>
>
> This came through dated March 17, and thunderbird "the dumbest mail
> client ever, except all the other ones" doesn't let me _not_ sort my
> mailboxes anymore, so the closest I can get is sorting by date.
>
> Translation: this stuff got bured way back in the history and I had to
> open the mbox file in vi just to confirm that it was a recent post and
> not historical.
>
> I take it your new "git format-patch | formail" workflow has a downside? :)
Sorry about that. The same should happen with git send-email though,
no? Sorry I'm not used to the tools for sending patch series as mail
threads rather than attachments. I can strip Date headers in the
future and let them get regenerated, but a good MUA should sort by
date received, not the sender's date headers.
Rich
next prev parent reply other threads:[~2016-04-29 0:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 23:09 [PATCH 1/7] sh: add support for J-Core J2 processor Rich Felker
2016-04-29 0:12 ` Rob Landley
2016-04-29 0:36 ` Rich Felker [this message]
2016-04-29 4:53 ` Rob Landley
2016-04-29 6:42 ` Geert Uytterhoeven
2016-04-29 6:48 ` Geert Uytterhoeven
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=20160429003646.GA21636@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=linux-sh@vger.kernel.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).