linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] generic arm for MSM
Date: Thu, 25 Mar 2010 16:21:47 -0700	[thread overview]
Message-ID: <1269559307.21793.78.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20100325225555.GL24984@n2100.arm.linux.org.uk>

On Thu, 2010-03-25 at 22:55 +0000, Russell King - ARM Linux wrote:
> On Thu, Mar 25, 2010 at 03:54:15PM -0700, Daniel Walker wrote:
> > On Thu, 2010-03-25 at 22:53 +0000, Russell King - ARM Linux wrote:
> > 
> > > http://www.home.arm.linux.org.uk/developer/
> > > 
> > > has a link to gitweb for it, and a url pointing to where it is on the
> > > ftp/http site:
> > > 
> > > # rmk's GIT tree
> > > # rmk's random kernel patches and git tree 
> > > 
> > > It's not like it's hidden.
> > 
> > for that url I get,
> > 
> > Forbidden
> > You don't have permission to access /developer/ on this server.
> 
> http://www.arm.linux.org.uk/developer/
> 
> sorry, I tend to use my own local copy of the site; the public copy is
> identical.

I guess it's not hidden, but I'd say it's not easy to find .. Is there
some reason you don't want that tree in the MAINTAINERS file ?

I tried to add both,

ftp://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-2.6-arm.git
http://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-2.6-arm.git/

and I got strange download failures ..

fatal: ftp://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-2.6-arm.git/info/refs download error - Failed connect to ftp.arm.linux.org.uk:21; Operation now in progress

Both had the same failure. I tried with a newer git version 1.7 (before
it was 1.6) and it showed this on the ftp variant,

error: RETR response: 550 (curl_result = 78, http_code = 550, sha1 = 01e77706cdde7c0b47e5ca1f4284a795504c7c40The command seems to be hund

However, it did finish downloading the tree ..

Are these known issues, or maybe it's because bits are traveling
US<->UK ?

Daniel

  reply	other threads:[~2010-03-25 23:21 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 [this message]
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=1269559307.21793.78.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).