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

Re: [PATCH] Add git-zip-tree to .gitignore

From
Junio C Hamano <junkio@cox.net>
Date
Aug 28, 2006, 22:43 UTC
Message-ID
<7vd5akqy5e.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<44F36E03.9090802@lsrfire.ath.cx>
Rene Scharfe <rene.scharfe@lsrfire.ath.cx> writes:
Show 20 quoted lines
> Junio C Hamano schrieb:
>> 
>> I was more worried about possibly having to do --remote once in
>> each for tar-tree and zip-tree in git-daemon.  The version of
>> daemon currently in "pu" can allow git-tar-tree to be accessed
>> from the client via git:// URL.
>
> Good point.  And especially for net transfers a compressed format like
> ZIP or TGZ (not yet implemented) would be better.
>
> Would it make sense to have just one multiplexer command?  I.e.
> something like this:
>
>   git-archive -f <format> [extra]                <tree-ish> [<base>]
>   git-archive -f <format> [extra] --upload       <tree-ish> [<base>]
>   git-archive -f <format> [extra] --remote=<url> <tree-ish> [<base>]
>
> [extra] stands for format specific options like the compression ratio
> for ZIP.  The protocol spoken by upload and --remote would need to be
> extended to be able to specify the format and any format specific options.

I think so. I never liked the --remote support that was done inside tar-tree myself and hoped there would be better ways.

Show 8 quoted lines
> While we're discussing the command line interface, would it make sense
> to support path specs, like e.g. ls-tree does?  Like this:
>
>   git-archive -f <format> [extra] [--prefix=<base>] <tree-ish> [<path>]
>
> Personally, I don't see the need for path specs for archive creation,
> but IF we want to introduce them then the best time to do it would be
> now, at the same time as introducing git-archive (or git-archive-tree).

Well people may want to say more than one <path> to archive only "include/asm-i386" and "arch/i386" directories, but other than that, naming <tree-ish> with <revision>:<path> syntax would be enough. But I agree with you that it would be now IF we want to do this. I am neutral, perhaps slightly in favor.

Previous: Rene Scharfe
Message 6 of 6 in “Add git-zip-tree to .gitignore”
  1. Add git-zip-tree to .gitignoreRene Scharfe, Aug 27, 2006
  2. Junio C HamanoAug 27, 2006
  3. Rene ScharfeAug 27, 2006
  4. Junio C HamanoAug 27, 2006
  5. Rene ScharfeAug 28, 2006
  6. Junio C HamanoAug 28, 2006

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.