Skip to contentSkip to conversation

git pull through http / git

DISCUSSION Nicolas Ferre 5 participants 9 messages Jul 7, 2008 – Jul 8, 2008

lore
Share & tools
lore
#0 lore raw

Hi,

I see differences when I use git to a git.kernel.org between the one I fetch using http protocol and the one shown through the gitweb interface.

I cloned (or git remote add) the mmc tree and my config shows this url :
url = http://www.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git

but I see updates in :
http://git.kernel.org/?p=linux/kernel/git/drzeus/mmc.git;a=summary
I cannot get.

I tried from several mirrors without success.

Thanks for your help, regards,

Signature · 1 line
Nicolas Ferre
#1 lore raw
Quoted 11 lines · Nicolas Ferre

Hi,

I see differences when I use git to a git.kernel.org between the one I fetch using http protocol and the one shown through the gitweb interface.

I cloned (or git remote add) the mmc tree and my config shows this url :
url = http://www.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git

but I see updates in :
http://git.kernel.org/?p=linux/kernel/git/drzeus/mmc.git;a=summary
I cannot get.

I don't think many care about http downloading, just because it is available as such.
git:// and rsync:// are available though and should be usable even without the http info that needs to be constantly refreshed when one wants to use http....

#2 lore raw
Quoted 4 lines · Jan Engelhardt

I don't think many care about http downloading, just because it is available as such.
git:// and rsync:// are available though and should be usable even without the http info that needs to be constantly refreshed when one wants to use http....

I thought rsync:// had the same problem (dumb transport) as http://.

I have made some sketches on a git-aware http protocol to deal with the "idiot IT department-managed firewall" problem; however, I have not had time to implement it.

-hpa

#3 lore raw
Quoted 9 lines · H. Peter Anvin
Quoted 6 lines · Jan Engelhardt

I don't think many care about http downloading, just because it is available as such.
git:// and rsync:// are available though and should be usable even without the http info that needs to be constantly refreshed when one wants to use http....

I thought rsync:// had the same problem (dumb transport) as http://.

I thought the opposite (read: no way to prove it).
rsync has a possibility to list a directory, whereas this is not possible with HTTP (you always get a fancy html index page or a Directory Listing Denied), hence it can figure out all objects that are possibly located in the repository.

Quoted 3 lines

I have made some sketches on a git-aware http protocol to deal with the "idiot IT department-managed firewall" problem; however, I have not had time to implement it.

Not wanting to downplay your work, but I'd be happier if they would not get to have their githttp in the hope that these IT departments get a clue that http is not a fits-it-all solution.

Because once the workers can't do their job because the world is Git-dominated, they have to turn it on. But maybe then they still don't get the clue...hmm
tricky situation :)

#4 lore raw
Quoted 10 lines · Jan Engelhardt
Quoted 2 lines

I have made some sketches on a git-aware http protocol to deal with the "idiot IT department-managed firewall" problem; however, I have not had time to implement it.

Not wanting to downplay your work, but I'd be happier if they would not get to have their githttp in the hope that these IT departments get a clue that http is not a fits-it-all solution.

Because once the workers can't do their job because the world is Git-dominated, they have to turn it on. But maybe then they still don't get the clue...hmm tricky situation :)

Given that one of the companies so affected is Intel, which you'd think would have more of a clue not just for git but for God-knows-how-many other services...

-hpa

#5 lore raw
In reply to Jan Engelhardt

Jan Engelhardt :

Quoted 10 lines · Nicolas Ferre
Quoted 9 lines

Hi,

I see differences when I use git to a git.kernel.org between the one I fetch using http protocol and the one shown through the gitweb interface.

I cloned (or git remote add) the mmc tree and my config shows this url :
url = http://www.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git

Quoted 6 lines
Quoted 3 lines

but I see updates in :
http://git.kernel.org/?p=linux/kernel/git/drzeus/mmc.git;a=summary
I cannot get.

I don't think many care about http downloading, just because it is available as such.
git:// and rsync:// are available though and should be usable even without the http info that needs to be constantly refreshed when one wants to use http....

If only I had the choice...

You certainly know why I am using http. This feature is very useful for me and I was wondering why it was out of sync with the web interface.

Regards,

Signature · 1 line
Nicolas Ferre
#6 lore raw

Keep in mind Kernel.org uses caching on gitweb and thus gitweb itself is not necessarily accurate / up to date. git.kernel.org also round-robins across 4 machines which may be in various states of update, so your fundamentally looking at a number of different possible points that may be slightly out of sync with each other.

- John 'Warthog9' Hawley
Chief Kernel.org Admin & Original Author of the Gitweb Caching code

Quoted 27 lines · Nicolas Ferre

Jan Engelhardt :

Quoted 14 lines · Nicolas Ferre
Quoted 6 lines

Hi,

I see differences when I use git to a git.kernel.org between the one I fetch using http protocol and the one shown through the gitweb interface.

Quoted 6 lines

I cloned (or git remote add) the mmc tree and my config shows this url :
url = http://www.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git

but I see updates in :
http://git.kernel.org/?p=linux/kernel/git/drzeus/mmc.git;a=summary
I cannot get.

Quoted 5 lines

I don't think many care about http downloading, just because it is available as such.
git:// and rsync:// are available though and should be usable even without the http info that needs to be constantly refreshed when one wants to use http....

If only I had the choice...

You certainly know why I am using http. This feature is very useful for me and I was wondering why it was out of sync with the web interface.

Regards,

#7 lore raw

J.H. :

Quoted 5 lines

Keep in mind Kernel.org uses caching on gitweb and thus gitweb itself is not necessarily accurate / up to date. git.kernel.org also round-robins across 4 machines which may be in various states of update, so your fundamentally looking at a number of different possible points that may be slightly out of sync with each other.

Ok, I understand.
I am talking about a 3 days old commit. Is this normal to have no update
from the http side ?
I yes, I will wait...

Regards,

Signature · 1 line
Nicolas Ferre
#8 lore raw
Quoted 7 lines · Nicolas Ferre

J.H. :

Quoted 5 lines

Keep in mind Kernel.org uses caching on gitweb and thus gitweb itself is not necessarily accurate / up to date. git.kernel.org also round-robins across 4 machines which may be in various states of update, so your fundamentally looking at a number of different possible points that may be slightly out of sync with each other.

Quoted 5 lines

Ok, I understand.
I am talking about a 3 days old commit. Is this normal to have no update
from the http side ?
I yes, I will wait...

You're trying to do a git pull via http (as opposed to gitweb)? Then that is dependent on the owner of the repository having enabled "git update-server-info".

Overall, avoid pulling git via http. It's just plain broken.

-hpa