linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@fifo99.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"Nicolas Pitre" <nico@fluxnic.net>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: RE: [GIT PULL] generic arm for MSM
Date: Tue, 06 Apr 2010 15:44:04 -0700	[thread overview]
Message-ID: <1270593844.9066.57.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B0270842697636D1FD94C@AUSP01VMBX24.collaborationhost.net>

On Tue, 2010-04-06 at 17:34 -0500, H Hartley Sweeten wrote:
> On Tuesday, April 06, 2010 3:09 PM, Daniel Walker wrote:
> > On Tue, 2010-04-06 at 23:04 +0100, Russell King - ARM Linux wrote:
> >>  
> >>> Does you server list anything wrong happening, cause those 550 errors
> >>> seem pretty suspect. It could also be some sort of firewall thing on my
> >>> end. I'm assuming no one else has reported anything like this before
> >>> right?
> >> 
> >> The 550 errors are because the unpacked objects don't exist; they're
> >> already inside one of Linus' pack files which you should already have.
> >> 
> >> That's the point - you should already have these git IDs (the ones you
> >> explicitly refer to) so there should be no reason for git to even
> >> consider fetching them via http or ftp.
> >
> > So your saying that the git defect .. I'm using a fairly recent version
> > of git 1.7.0 .. There are slightly more recent ones which I can try
> > also.
> 
> Daniel,
> 
> I just updated my copy of Russell's tree with no issues:
> 
>  $ git remote update
> Fetching origin
> Fetching linux-arm
> From http://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-2.6-arm
>    988addf..b72c409  devel-stable -> linux-arm/devel-stable
>  * [new branch]      lmb        -> linux-arm/lmb
>    bb45692..c6c3523  master     -> linux-arm/master
>    ae6be51..2eaa9cf  origin     -> linux-arm/origin
> 
> Are you trying to 'git pull' his tree?

No, it's remote so I do either "git fetch rmk" , or "git remote update
rmk"

> I tried that initially and it worked fine for the initial pull.  After that I
> always ran into issues with trying to update it.
> 
> I don't quite remember how I did the initial pull when I started a new branch
> to follow Russell's tree but I think I did it like the FAQ says on how to
> follow the -next tree.
> 
> Oh, this is using git version 1.7.0.3.254.g4503b

Did you ever try this on 1.7.0 ?

Daniel


  reply	other threads:[~2010-04-06 22:44 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
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 [this message]
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=1270593844.9066.57.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@fifo99.com \
    --cc=hartleys@visionengravers.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nico@fluxnic.net \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).