From: jk@ozlabs.org (Jeremy Kerr)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v3]Update broken web addresses.
Date: Wed, 22 Sep 2010 21:06:45 +0800 [thread overview]
Message-ID: <1285160805.2796.0.camel@pororo> (raw)
In-Reply-To: <20100922105852.GC4710@linux-mips.org>
Hi Ralf,
> On Tue, Sep 21, 2010 at 06:29:16PM -0700, Justin P. Mattock wrote:
> > Date: Tue, 21 Sep 2010 18:29:16 -0700
> > From: "Justin P. Mattock" <justinmattock@gmail.com>
> > To: trivial at kernel.org
> > Cc: linux-arm-kernel at lists.infradead.org, linux-kernel at vger.kernel.org,
> > linux-omap at vger.kernel.org, linux-m32r at ml.linux-m32r.org,
> > linux-m68k at lists.linux-m68k.org, linux-mips at linux-mips.org,
> > linuxppc-dev at lists.ozlabs.org, linux-laptop at vger.kernel.org, "Justin P.
> > Mattock" <justinmattock@gmail.com>, "Maciej W. Rozycki"
> > <macro@linux-mips.org>, Finn Thain <fthain@telegraphics.com.au>, Randy
> > Dunlap <rdunlap@xenotime.net>
> > Subject: [PATCH 1/2 v3]Update broken web addresses.
> > Content-Type: text/plain; charset=UTF-8
>
> Patchwork MIME butchers the subject of this patch, see
>
> https://patchwork.linux-mips.org/patch/1587/
> https://patchwork.kernel.org/patch/198382/
>
Thanks for the heads-up - I'll see what's happening with the header
decoding here.
Cheers,
Jeremy
prev parent reply other threads:[~2010-09-22 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 1:29 [PATCH 1/2 v3]Update broken web addresses Justin P. Mattock
2010-09-22 1:29 ` [PATCH 2/2 v3]Update broken web addresses archive dot org only Justin P. Mattock
2010-09-22 3:25 ` [PATCH 1/2 v3]Update broken web addresses Finn Thain
2010-09-22 3:57 ` Justin P. Mattock
2010-09-22 10:58 ` Ralf Baechle
2010-09-22 13:06 ` Jeremy Kerr [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=1285160805.2796.0.camel@pororo \
--to=jk@ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.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).