From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-omap@vger.kernel.org
Subject: Re: git-pull-request for omap2-upstream branch for next merge window (Was: [PATCH 00/16] Omap2 patches for post 2.6.26)
Date: Tue, 26 Aug 2008 09:06:16 +0100 [thread overview]
Message-ID: <20080826080616.GC24147@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080823233711.GM4713@atomide.com>
On Sat, Aug 23, 2008 at 04:37:12PM -0700, Tony Lindgren wrote:
> Here's the pull request for you assuming your don't have other comments.
>
> I'll be out of town next week, so if there are other comments I won't
> be able to refresh the patches until I get back.
>
> Regards,
>
> Tony
>
>
> The following changes since commit dcac5512382d8df4476ce2e9c13e9540b3801d32:
> Russell King (1):
> Merge branch 'omap2-clock' of git://git.kernel.org/.../tmlind/linux-omap-2.6.git
This is why I don't want to publish my git tree. You're the second person
to base their tree off my devel branch.
The devel branch is _constantly_ remerged. Basing your tree on it will
mean I can't merge it. Please don't. Base it either on something in
Linus' tree _or_ something you've already asked me to pull.
If this continues, I'll go back to only publishing my git tree in diff
and mbox form.
next prev parent reply other threads:[~2008-08-26 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 21:23 [PATCH 00/16] Omap2 patches for post 2.6.26 Russell King - ARM Linux
2008-08-20 7:23 ` Tony Lindgren
2008-08-23 23:37 ` git-pull-request for omap2-upstream branch for next merge window (Was: [PATCH 00/16] Omap2 patches for post 2.6.26) Tony Lindgren
2008-08-26 8:06 ` Russell King - ARM Linux [this message]
2008-08-26 16:01 ` Nicolas Pitre
2008-08-26 16:26 ` Russell King - ARM Linux
2008-08-26 17:34 ` Nicolas Pitre
2008-08-26 18:28 ` Nicolas Pitre
2008-08-26 18:49 ` Russell King - ARM Linux
2008-09-02 22:21 ` Tony Lindgren
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=20080826080616.GC24147@flint.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--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