From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: linux-fbdev@vger.kernel.org,
Dimitry Torokhov <dmitry.torokhov@gmail.com>,
trivial@kernel.org, Mike Frysinger <vapier.adi@gmail.com>,
linux-scsi@vger.kernel.org, linux-usb@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-ide@vger.kernel.org,
Randy Dunlap <rdunlap@xenotime.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Matt Turner <mattst88@gmail.com>,
alsa-devel@alsa-project.org
Subject: Re: [RFC v5]update broken web addresses in the kernel.
Date: Tue, 28 Sep 2010 06:41:22 -0700 [thread overview]
Message-ID: <4CA1F082.2010900@gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.00.1009281713410.276@localhost>
On 09/28/2010 12:35 AM, Finn Thain wrote:
>
> On Tue, 28 Sep 2010, Justin P. Mattock wrote:
>
>> o.k... I'll make the changes to the arch patch, and combine the two, and
>> send it to jiri..
>
> Why?
>
> My advice is don't do it unless you want to waste reviewers' time.
>
>> as for the names and signed offs is what is below fine or do I need to
>> change some of them?
>
> If you combine patch 1 and patch 2 and submit that as patch 3, you will
> likely have to CC patch 3 to everyone to whom you sent patch 1 plus
> everyone to whom you sent patch 2. You must also change any "acked-by" to
> "Cc", since patch 3 is new.
>
> Keep the same CC list since Jiri is already on it ("trivial@kernel.org").
>
> Finn
>
alright.. so it will be two patches then..(not the best at the CC etc..
thing) cool... and thanks again for reviewing this for me..(back
breaking work, but somebodies _gots_ to do it..)
Justin P. Mattock
prev parent reply other threads:[~2010-09-28 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 4:19 [RFC v5]update broken web addresses in the kernel Justin P. Mattock
2010-09-28 6:22 ` Finn Thain
2010-09-28 7:05 ` Justin P. Mattock
2010-09-28 7:35 ` Finn Thain
2010-09-28 13:41 ` Justin P. Mattock [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=4CA1F082.2010900@gmail.com \
--to=justinmattock@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mattst88@gmail.com \
--cc=rdunlap@xenotime.net \
--cc=trivial@kernel.org \
--cc=vapier.adi@gmail.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;
as well as URLs for NNTP newsgroup(s).