Git development
 help / color / mirror / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: John Wiegley <johnw@newartisans.com>
Cc: git@vger.kernel.org
Subject: Re: Problem with git fetch over http://
Date: Fri, 25 Apr 2008 18:04:16 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.1.00.0804251749390.19665@iabervon.org> (raw)
In-Reply-To: <63F7B390-32D1-458A-8ED9-D5AC62F46745@newartisans.com>

On Fri, 25 Apr 2008, John Wiegley wrote:

> Hello, I'm using the Builtbot to pull sources from a Git repository, and have
> found that the Buildbot's Git step always uses git-fetch -- a detail of
> Buildbot which I currently have little control over.
> 
> This is no problem if the git:// protocol is used, but using fetch with
> http:// doesn't work.  This has been mentioned elsewhere:
> 
>  http://lists.berlios.de/pipermail/bitbake-dev/2007-November/000765.html
> 
> Here's a quick example of what I mean:
> 
>  cd /tmp ; mkdir foo ; cd foo ; git init
> 
>  git fetch git://newartisans.com/ledger.git	# works fine
> 
>  cd /tmp ; rm -fr foo ; mkdir foo ; cd foo ; git init
> 
>  git fetch http://newartisans.com/git/ledger.git  # fails
> 
> This is happening with git-1.5.5 on the server, Apache 2.2 and git-1.5.5.1 on
> the client.

John mentioned on IRC that clone works.

$ git-ls-remote http://newartisans.com/git/ledger.git
96751442d9eda537480867e599e4c604663f4530        refs/heads/master
365baca5174232cc35e4ed190fd8ce93c3611c84        refs/heads/v2.4.1
f972a89073843fdbb2a1bef969d9ca70509d4bfe        refs/heads/v2.5
6a81d760dc4ab9028b27430124702c28c0b894ed        refs/tags/cvs-20040410
fed3956a310a2ea8c8595b7fde7aaa0623492ca6        refs/tags/v0.1
...

$ git-ls-remote git://newartisans.com/ledger.git
96751442d9eda537480867e599e4c604663f4530        HEAD
96751442d9eda537480867e599e4c604663f4530        refs/heads/master
365baca5174232cc35e4ed190fd8ce93c3611c84        refs/heads/v2.4.1
f972a89073843fdbb2a1bef969d9ca70509d4bfe        refs/heads/v2.5
6a81d760dc4ab9028b27430124702c28c0b894ed        refs/tags/cvs-20040410
fed3956a310a2ea8c8595b7fde7aaa0623492ca6        refs/tags/v0.1
...

Looks like either server-info.c:update_info_refs() needs to also list 
HEAD, or transport.c:get_refs_via_curl() needs to guess that $url/HEAD 
exists and fetch it to add to the list, or both.

	-Daniel
*This .sig left intentionally blank*

  parent reply	other threads:[~2008-04-25 22:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25 20:42 Problem with git fetch over http:// John Wiegley
2008-04-25 21:24 ` Junio C Hamano
2008-04-25 21:34   ` Mike Hommey
2008-04-25 22:04 ` Daniel Barkalow [this message]
2008-04-25 22:29   ` Junio C Hamano
2008-04-25 23:35     ` Daniel Barkalow

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=alpine.LNX.1.00.0804251749390.19665@iabervon.org \
    --to=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=johnw@newartisans.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