From: Justin Mattock <justinmattock@gmail.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: trivial@kernel.org, johannes@sipsolutions.net,
davem@davemloft.net, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 18/21]include:net:mac80211.h remove one to many l's in the word.
Date: Thu, 24 Feb 2011 23:10:15 -0800 [thread overview]
Message-ID: <C0CEB11E-CD60-4A10-BFC8-7CB555D1413C@gmail.com> (raw)
In-Reply-To: <AANLkTi=FuD0FCTv6f0sPKkg14O9R_giKi9uvA0Xsgy1q@mail.gmail.com>
On Feb 24, 2011, at 10:20 PM, Julian Calaby wrote:
> On Fri, Feb 25, 2011 at 17:15, Justin P. Mattock
> <justinmattock@gmail.com> wrote:
>> The patch below removes an extra "l" in the word.
>
> Random thought:
>
> Not that I'm complaining about your work here, and not that commits
> are a finite resource, but would it be possible for you to collect
> your spelling changes into slightly bigger commits before sending them
> off?
>
> E.g. instead of sending off 21 patches to remove 21 erroneous l's, why
> not do a full spelling check on these 21 files, then send off 21
> patches to fix *all* the spelling mistakes in each file? You could
> even group them up by directory if you liked.
>
> Thanks,
>
> --
>
> Julian Calaby
>
> Email: julian.calaby@gmail.com
> Profile: http://www.google.com/profiles/julian.calaby/
> .Plan: http://sites.google.com/site/juliancalaby/
yeah.. I agree, its just people have said that I should individually
send each patch to each maintainer subsystem etc...
(rather would just send one with everything on it, but then might make
things more confusing)
Justin P. Mattock
next prev parent reply other threads:[~2011-02-25 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 6:15 Justin P. Mattock
2011-02-25 6:20 ` Julian Calaby
2011-02-25 7:10 ` Justin Mattock [this message]
2011-02-25 8:55 ` Johannes Berg
2011-02-25 8:20 ` Jiri Kosina
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=C0CEB11E-CD60-4A10-BFC8-7CB555D1413C@gmail.com \
--to=justinmattock@gmail.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=julian.calaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=trivial@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
all inboxes | Powered by JetHome®