linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@codeaurora.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org
Subject: Re: [GIT PULL] generic arm for MSM
Date: Thu, 25 Mar 2010 15:32:58 -0700	[thread overview]
Message-ID: <1269556378.21793.47.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20100325222959.GI24984@n2100.arm.linux.org.uk>

On Thu, 2010-03-25 at 22:29 +0000, Russell King - ARM Linux wrote:
> On Thu, Mar 25, 2010 at 02:52:17PM -0700, Daniel Walker wrote:
> > These are all mostly small patches that I've sent out a few times with
> > no comments. Let me know if you see any issues.
> > 
> > The following changes since commit 7ee744f22ffad619e23912a22d1b2795e10ed825:
> >   Stephen Rothwell (1):
> >         Add linux-next specific files for 20100324
> 
> This doesn't seem to be in Linus' tree - ah, no, it's based on linux-next.
> So, if I pull this, I get everyone's work into my tree.  To see what
> you're actually sending me, do this:
> 
> 	git diff --stat 9353685..
> 
> and it'll show you what you're sending me which isn't in my 'devel' branch
> already - and if you replace that git id with the latest Linus' commit in
> your tree...
> 
> So no thanks.  Will not pull the entire linux-next tree into mine.

Oh please why not! (just joking) ..

> Please build your tree on a more stable base, such as Linus' tree.

I thought you wanted stuff on your development tree? Where can I get
that other than in next? It's easy enough to put it on a linus tree if
that's acceptable.

Daniel


  reply	other threads:[~2010-03-25 22:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 21:52 [GIT PULL] generic arm for MSM Daniel Walker
2010-03-25 22:29 ` Russell King - ARM Linux
2010-03-25 22:32   ` Daniel Walker [this message]
2010-03-25 22:42     ` Russell King - ARM Linux
2010-03-25 22:46 ` Nicolas Pitre
2010-03-25 22:49   ` Daniel Walker
2010-03-25 22:53     ` Russell King - ARM Linux
2010-03-25 22:54       ` Daniel Walker
2010-03-25 22:55         ` Russell King - ARM Linux
2010-03-25 23:21           ` Daniel Walker
2010-03-26  8:14             ` Uwe Kleine-König
2010-03-26  8:23               ` Russell King - ARM Linux
2010-03-26  9:30                 ` Uwe Kleine-König
2010-04-01 23:11                 ` Daniel Walker
2010-04-06 21:35                   ` Russell King - ARM Linux
2010-04-06 22:00                     ` Daniel Walker
2010-04-06 22:04                       ` Russell King - ARM Linux
2010-04-06 22:08                         ` Daniel Walker
2010-04-06 22:34                           ` H Hartley Sweeten
2010-04-06 22:44                             ` Daniel Walker
2010-03-26 13:33               ` Daniel Walker
2010-03-26 11:24     ` Mark Brown

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=1269556378.21793.47.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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).