From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, tony@atomide.com,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: OMAP clock fast-forward: an introduction to six series
Date: Wed, 28 Jan 2009 21:18:44 +0000 [thread overview]
Message-ID: <20090128211844.GI23301@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.0901281310590.14710@utopia.booyaka.com>
On Wed, Jan 28, 2009 at 01:22:22PM -0700, Paul Walmsley wrote:
> Per rmk's preferences, some patches have been 'compressed.' That is, some
> fix patches have been rolled into a single patch with the original. To
> ease cross-referencing with the linux-omap git tree, original commit IDs
> have been inserted into the patch messages. Also, what would have been an
> extremely long series has been split into six smaller, cumulative, roughly
> thematic patch series. If requested, I would be pleased to simply send
> one large series of the original, uncompressed patches. Thanks to the git
> and stgit authors and contributors: without those tools, this process
> would have been nearly impossible.
Since this patch series was only really meant for me to do some follow-on
work on it (to merge it into my tree) is it really necessary to submit
this 70 patch series via slow email via several mailing lists?
At the rate they're coming through I might have the entire set by
midnight...
next prev parent reply other threads:[~2009-01-28 21:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 20:22 Paul Walmsley
2009-01-28 21:18 ` Russell King - ARM Linux [this message]
2009-01-29 7:05 ` Paul Walmsley
2009-01-29 8:11 ` Russell King - ARM Linux
2009-01-29 8:30 ` Russell King - ARM Linux
2009-01-29 16:25 ` Tony Lindgren
2009-01-29 16:35 ` Russell King - ARM Linux
2009-01-29 16:41 ` Tony Lindgren
2009-01-29 16:53 ` Tony Lindgren
2009-01-29 17:14 ` Russell King - ARM Linux
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=20090128211844.GI23301@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®