All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard MUSIL <richard.musil@st.com>
To: Willy Tarreau <w@1wt.eu>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: Problem with accessing stable git over http
Date: Fri, 04 Apr 2008 10:29:53 +0200	[thread overview]
Message-ID: <47F5E701.6020706@st.com> (raw)
In-Reply-To: <20080404050718.GE23796@1wt.eu>

On 4.4.2008 7:07, Willy Tarreau wrote:
> On Wed, Mar 26, 2008 at 11:35:16AM +0100, Richard MUSIL wrote:
>> For some reason I cannot access stable kernel git branches over http
>> since version 2.6.23.y.
>>
>> HTTP access is working for 2.6.22.y
>> (http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.22.y.git)
>> - I can fetch from it. It is also working for Linus' dev branch
>> (http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git)
>> which I clone.
>> But for stable 2.6.23.y and 2.6.24.y, when I try fetch, I get in particular:
>>
>> HTTP GET
>> http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.24.y.git/info/refs
>> HTTP/1.1
>> HTTP HTTP/1.1 404 Not Found (text/html)
>>
>> I am behind proxy and firewall and I cannot use git protocol.
>>
>> Does anyone know, what might be a problem? It kind of makes the sources
>> unreachable for me :(.
> 
> what version of git are you using ? Those files indeed do not exist in
> either repository, so it would be good to find why git tries to fetch
> them.

I am usually using latest version compiled on gentoo from ~x86
(currently it is 1.5.4.5).

Interestingly those files exist for linux-2.6.22.y, i.e. accessing
http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.22.y.git/info/refs
gives something and that is probably why I can fetch from 2.6.22.y branch.

Why git tries to access it is something beyond my understanding, I guess
it is the way http access works.

But I wonder, why the similar file is not present on 2.6.23.y and
2.6.24.y branch. My git config for project looks like this:

> [core]
>         repositoryformatversion = 0
>         filemode = true
>         bare = false
>         logallrefupdates = true
> [remote "origin"]
>         url = http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>         fetch = +refs/heads/*:refs/remotes/origin/*
> [branch "master"]
>         remote = origin
>         merge = refs/heads/master
> [remote "linux-2.6.22.y"]
>         url = http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.22.y.git
>         fetch = +refs/heads/*:refs/remotes/linux-2.6.22.y/*
> [remote "linux-2.6.24.y"]
>         url = http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.24.y.git
>         fetch = +refs/heads/*:refs/remotes/linux-2.6.24.y/*

So there is clearly discrepancy between those two on the server, but
whether this is a bug or intentional I do not know.

Richard

  reply	other threads:[~2008-04-04  8:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 10:35 Problem with accessing stable git over http Richard MUSIL
2008-04-04  5:07 ` Willy Tarreau
2008-04-04  8:29   ` Richard MUSIL [this message]
2008-04-15 12:54     ` Richard MUSIL
2008-04-17 21:28       ` Greg KH
2008-04-18  7:18         ` Richard MUSIL
2008-05-27 10:11         ` Richard MUSIL
2008-05-27 16:54           ` Greg KH

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=47F5E701.6020706@st.com \
    --to=richard.musil@st.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.