git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Re: git-http-pull broken in latest git

From
Junio C Hamano <junkio@cox.net>
Date
Aug 12, 2005, 05:20 UTC
Message-ID
<7vll37afz4.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.63.0508112256430.12816@iabervon.org>
Daniel Barkalow <barkalow@iabervon.org> writes:
> Petr Baudis <pasky@suse.cz> writes:
>> Yes, but cg-clone doesn't - it naively depended on the core git tools
>> actually, er.. working. ;-)

Sorry about that. I used to have a wrapper to deal with packs around http-pull before Daniel's pack enhancement, and yanking it before really checking that enhanced http-pull actually worked was my fault as well.

>> This became a nightmare to me by now - on two machines I tried to pull
>> to over HTTP, that failed miserably, and I got stuck until I applied
>> Daniel's patch there (and cleaned up after previous git-http-pulls).

I'll push one out with two patches from Daniel today in short order. Currently running the final "make test" round.

> At some point, I have to revisit getting git-ssh-* to generate exactly the 
> required pack and transfer that, but that's an efficiency issue, not a 
> correctness one, and shouldn't be relevant to the problem you're having.

Wouldn't enhancing ssh-push to generate packs on the fly involve reinventing send-pack and/or upload-pack?

If send-pack/receive-pack pair for the push side, and/or fetch&clone-pack/upload-pack pair for the pull side does not work as well as you would want, then ssh-push/pull pair may still be a useful tool, at the same time that means send-pack and upload-pack should be fixed to address the problem you have with them. But if that is not the case, then it might be better to declare that ssh-pull/push pair has outlived its usefulness.

The same thing can be said about local-pull to a lesser degree. Lesser because people, including Pasky who said so on the list recently, would like its hard-linking behaviour, and its not exploding the existing packs, which send-pack and upload-pack would not give. So I would rate local-pull higher than ssh-push/pull on the priority scale if I were doing them.

Previous: Daniel BarkalowNext: Daniel Barkalow
Message 10 of 11 in “cg-clone http://www.kernel.org/pub/scm/git/git.git fails”
  1. Dirk BehmeAug 9, 2005
  2. git-http-pull broken in latest gitPetr Baudis, Aug 11, 2005
  3. Junio C HamanoAug 11, 2005
  4. Re: git-http-pull broken in latest gitDaniel Barkalow, Aug 11, 2005
  5. Junio C HamanoAug 12, 2005
  6. Daniel BarkalowAug 12, 2005
  7. Junio C HamanoAug 11, 2005
  8. Petr BaudisAug 12, 2005
  9. Re: git-http-pull broken in latest gitDaniel Barkalow, Aug 12, 2005
  10. Junio C HamanoAug 12, 2005
  11. Daniel BarkalowAug 12, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.