From: Colin Ian King <colin.king@canonical.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jffs2: fix spelling mistake: "requestied" -> "requested"
Date: Wed, 19 Apr 2017 19:40:25 +0100 [thread overview]
Message-ID: <1ba1a663-f69e-b60e-0214-930a874ed78e@canonical.com> (raw)
In-Reply-To: <20170419183839.GA142791@google.com>
On 19/04/17 19:38, Brian Norris wrote:
> On Wed, Apr 19, 2017 at 11:36:34AM -0700, Brian Norris wrote:
>> s/an nonexistent/a nonexisten/
>
> Ha, and of course a typo in my correction :) But at least I didn't make
> that mistake in the real commit.
Easily done :-/
>
> Brian
>
Thanks Brian
prev parent reply other threads:[~2017-04-19 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 0:34 [PATCH] jffs2: fix spelling mistake: "requestied" -> "requested" Colin King
2017-04-19 18:36 ` Brian Norris
2017-04-19 18:38 ` Brian Norris
2017-04-19 18:40 ` Colin Ian King [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=1ba1a663-f69e-b60e-0214-930a874ed78e@canonical.com \
--to=colin.king@canonical.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@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).