Rene Scharfe <rene.scharfe@xxxxxxxxxxxxxx> writes:
> Junio C Hamano schrieb:
>> Although it was my fault applying it already to "master" without
>> asking this question first, I started to wonder how many more archive
>> format people would want, and if it might make more sense to
>> consolidate git-*-tree into a single frontend with an option to
>> specify the archiver.
>>
>> We would obviously need to keep git-tar-tree as a backward
>> compatibility alias for "git archive-tree -f tar", but doing things
>> that way we do not have to introduce unbounded number of new
>> git-{zip,rar,...}-tree programs.
>
> That thought occurred to me, too. I guess there are not that many more
> interesting archive formats, though. Can we defer adding
> git-archive-tree until a third archive format command appears? I won't
> submit another one, I promise. ;-)
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.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html