Re: Add git-archive [take #2]

[Junio C Hamano <junkio@cox.net>]

Franck Bui-Huu <vagabon.xyz@gmail.com> writes:

> Sorry I was speaking about the git protocol. It has been included
> in master branch.

I do not think so.  The recent "master" history is like this
(look at "gitk --full-history v1.4.2..master -- daemon.c"):

d819e4e daemon: prepare for multiple services

This introduced the daemon_service[] table and run_service
facility.  The service table contained upload-pack only.

This was merged into "master" and pushed out with 

1efca00 Merge early part of branch 'jc/daemon'

At this point, 'jc/daemon' topic branch contained the d819e4e
above and this one, which added upload-tar to the service table:

74c0cc2 daemon: add upload-tar service.

this was part of "next" but was not in "master".  This made
"tar-tree --remote" against git-daemon usable in "next".  But
before I pushed this out to "master", upload-archive design you
and Rene were working on became a lot more promising and
attractive.  Especially, discussion with Rene made me realize
that redoing upload-xxx protocol for each archiver was not a
good design.  So I did:

d9edcbd Revert "daemon: add upload-tar service."

on 'jc/daemon' branch.  And then that topic was merged into
"master" and pushed out, because that will allow you and Rene to
work your patch against "master" which would be nicer to not
just you but to everybody -- other people can test your patches
before they hit my tree on any branch.

In other words,

> 	git tar-tree --remote=git://anything/repo.git

never worked in "master".  At least that is how I wanted the
commit ancestry graph to look like and why the above merges and
reverts were done in the order described above.

Once git archive hits "master", we should announce that "git
tar-tree" and "git zip-tree" are deprecated, and we will remove
them sometime later.  As part of the same announcement we could
say that "git tar-tree --remote" works with transports other
than git-daemon, but we do not plan to add git native transport
support to it before its removal, because "git archive" is
preferred method both on local and remote archiving from then
on.