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

Re: How to clone-pack the HEAD?

From
Petr Baudis <pasky@suse.cz>
Date
Dec 15, 2005, 01:32 UTC
Message-ID
<20051215013201.GD10680@pasky.or.cz>
In-Reply-To
<7vfyovtaub.fsf@assigned-by-dhcp.cox.net>

Dear diary, on Thu, Dec 15, 2005 at 02:20:28AM CET, I got a letter where Junio C Hamano <junkio@cox.net> said that...

Show 7 quoted lines
> Petr Baudis <pasky@ucw.cz> writes:
> 
> >   (i) git-clone-pack url HEAD doesn't work
> 
> "clone-pack url branchname" might work, but the thing is, nobody
> uses clone-pack with explicit heads arguments so if HEAD does
> not work I am not surprised at all.
..snip..
Show 6 quoted lines
> I think extending git-fetch-pack to optionally keep things
> packed would be somewhat painful but the right approach.  Less
> painful and readily doable would be to run clone-pack as is, and
> reorganize the result of "copy of the remote" yourself.  That
> would be a straightforward thing to do if you are using it for
> the initial cloning.

Except that I cannot do the guessing git-clone-pack does (without fetching all the branches) - so I guess I'll make a patch tomorrow which fixes git-clone-pack ... HEAD (probably by checking in write_one_ref() whether it is looking at a symlink and following it first if that's the case) and then in Cogito do

	git-symbolic-ref HEAD refs/heads/origin

before git-clone-pack (and repoint HEAD back after it's over). That should do exactly what I need it to, I think.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 10 in “How to clone-pack the HEAD?”
  1. Petr BaudisDec 15, 2005
  2. Junio C HamanoDec 15, 2005
  3. Petr BaudisDec 15, 2005
  4. Junio C HamanoDec 15, 2005
  5. Junio C HamanoDec 15, 2005
  6. Junio C HamanoDec 15, 2005
  7. Junio C HamanoDec 15, 2005
  8. Petr BaudisDec 18, 2005
  9. Petr BaudisDec 18, 2005
  10. Petr BaudisDec 15, 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.