From: Grant Likely <grant.likely@secretlab.ca>
To: Joe Perches <joe@perches.com>,
Masayuki Ohtake <masa-korg@dsn.okisemi.com>
Cc: Linus Walleij <linus.ml.walleij@gmail.com>,
meego-dev@meego.com, LKML <linux-kernel@vger.kernel.org>,
David Brownell <dbrownell@users.sourceforge.net>,
qi.wang@intel.com, yong.y.wang@intel.com,
andrew.chih.howe.khor@intel.com, arjan@linux.intel.com,
gregkh@suse.de, Tomoya MORINAGA <morinaga526@dsn.okisemi.com>,
Thomas Gleixner <tglx@linutronix.de>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_SPI driver to 2.6.35
Date: Thu, 09 Sep 2010 19:41:46 -0600 [thread overview]
Message-ID: <e313fc89-de12-41fd-8f36-edd9b5dd6906@email.android.com> (raw)
In-Reply-To: <1284082229.24986.253.camel@Joe-Laptop>
"Joe Perches" <joe@perches.com> wrote:
>On Fri, 2010-09-10 at 09:27 +0900, Masayuki Ohtake wrote:
>> > If you incluse ChangeLogs it's easier to follow the development,
>> > thanks.
>> The latest patch has included the following Changelog.
>
>I believe Linus is asking for the same thing as I did.
>
>Some means to track your the changes in your multiple submissions
>of the same files.
>
>Typically, this would be a git repository where people can
>read the delta patches instead of entire unversioned files.
Nah, that's unnecessary overkill. A short description in the changelog about what has changed between each posted version of the patch is sufficient. I certainly don't ask anybody else to publish a git tree.
g.
>
>cheers, Joe
>
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2010-09-10 1:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 5:50 Masayuki Ohtake
2010-09-09 20:58 ` Linus Walleij
2010-09-10 0:27 ` Masayuki Ohtake
2010-09-10 1:30 ` Joe Perches
2010-09-10 1:41 ` Grant Likely [this message]
2010-09-10 2:05 ` Grant Likely
2010-09-10 4:55 ` Grant Likely
2010-09-14 2:52 ` Tomoya MORINAGA
2010-09-14 2:56 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2010-09-06 11:09 Masayuki Ohtak
2010-09-10 6:03 ` Grant Likely
[not found] <4C80E2D5.1020104@dsn.okisemi.com>
2010-09-03 14:46 ` Grant Likely
2010-09-03 17:50 ` Linus Walleij
2010-09-03 17:57 ` Grant Likely
2010-09-06 6:19 ` Masayuki Ohtake
2010-09-08 19:40 ` Grant Likely
[not found] <4C77BD91.9070302@dsn.okisemi.com>
2010-08-27 18:33 ` Grant Likely
2010-08-27 18:53 ` Thomas Gleixner
2010-08-27 18:54 ` Arjan van de Ven
2010-08-27 19:06 ` Thomas Gleixner
2010-08-27 19:20 ` Grant Likely
2010-08-30 7:28 ` Masayuki Ohtake
2010-08-30 12:44 ` Thomas Gleixner
2010-08-31 1:05 ` Masayuki Ohtake
2010-08-31 5:51 ` Grant Likely
2010-08-31 6:24 ` Masayuki Ohtake
2010-08-30 18:23 ` Grant Likely
2010-08-31 1:45 ` Masayuki Ohtake
2010-08-31 6:03 ` Grant Likely
2010-08-31 6:47 ` Masayuki Ohtake
2010-08-31 6:53 ` Grant Likely
2010-08-31 6:57 ` Masayuki Ohtake
2010-08-31 12:09 ` Masayuki Ohtake
[not found] <4C6131C2.4080101@dsn.okisemi.com>
2010-08-10 17:10 ` Greg KH
2010-08-11 1:25 ` Wang, Qi
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=e313fc89-de12-41fd-8f36-edd9b5dd6906@email.android.com \
--to=grant.likely@secretlab.ca \
--cc=andrew.chih.howe.khor@intel.com \
--cc=arjan@linux.intel.com \
--cc=dbrownell@users.sourceforge.net \
--cc=dwmw2@infradead.org \
--cc=gregkh@suse.de \
--cc=joe@perches.com \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masa-korg@dsn.okisemi.com \
--cc=meego-dev@meego.com \
--cc=morinaga526@dsn.okisemi.com \
--cc=qi.wang@intel.com \
--cc=tglx@linutronix.de \
--cc=yong.y.wang@intel.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
Powered by JetHome