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

Re: Passing commit IDs to git-archive

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 9, 2012, 22:34 UTC
Message-ID
<7vhaxx4d5s.fsf@alter.siamese.dyndns.org>
In-Reply-To
<8fb14091-99dc-4383-9cab-5bf508e0a554@mail>
Stephen Bash <bash@genarts.com> writes:
Show 7 quoted lines
> Unfortunately I just attempted
>
>   warp:bar bash$ git archive --remote=file:///Users/bash/Development/foo \
>                              --output=test.tgz 3b9e49b \
>                              path/to/subdir
>
> Thoughts?  Thanks in advance!

If you are always fetching from that same location, perhaps doing this only once

	git clone file:///...
and then every time you want to use the test.tgz, do something like
	git fetch
        git archive --output=test.tgz 3b9e49b path/to/subdir
or something like that?
Previous: Stephen BashNext: René Scharfe
Message 2 of 5 in “Passing commit IDs to git-archive”
  1. Stephen BashMar 9, 2012
  2. Junio C HamanoMar 9, 2012
  3. René ScharfeMar 10, 2012
  4. Jeff KingMar 12, 2012
  5. Stephen BashMar 12, 2012

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.