From: "Franck Bui-Huu" <vagabon.xyz@gmail.com>
To: "Rene Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: "Git Mailing List" <git@vger.kernel.org>,
"Junio C Hamano" <junkio@cox.net>
Subject: Re: [PATCH][RFC] Add git-archive-tree
Date: Sat, 2 Sep 2006 22:13:14 +0200 [thread overview]
Message-ID: <cda58cb80609021313p5156a14du4895e53387dd24dc@mail.gmail.com> (raw)
In-Reply-To: <44F982BD.1050509@lsrfire.ath.cx>
2006/9/2, Rene Scharfe <rene.scharfe@lsrfire.ath.cx>:
> The two patches I sent are what I have been able to come up with so far.
> The next step would be to add archive-neutral upload and download support.
>
> Having thought a bit about it I propose to keep git-archive-tree for
> local operations, only. It can be called by the uploader just like
Well I don't see why putting the remote operations in an other file. I
was more thinking on something like this:
git-archive --format=<fmt> [--remote=<repo>] <tree-ish> [path...]
This main porcelain function would call directly functions provided by
archivers lib. We will need to define an API which git-archive will
use for local operations.
Symetrically, on the sever side we would have:
git-upload-archive --format=<fmt> <repo> [path...]
used by git-daemon. It will deal with protocol, paths and use archiver's lib.
Eventually, we would have 2 commands:
git-archive
git-upload-archive
and get ride of
git-tar-tree
git-zip-tree
git-upload-tar
git-upload-zip
> git-tar-tree is now called by git-upload-tar. As Franck suggested, the
> uploader should allow the list of archive formats it supports to be
> restricted in a config file. The range of allowed compression levels
> should also be configurable.
>
> Does it make sense to change the wire protocol to simply send the
> command line options one by one?
That would make sense if the number of options grow up. Currently the
remote protocol had been written by Junio, I just pick up that part
from git-tar-tree and put it into git-archive. But if we allow
pathspec for remote operations, then we need to send them to the
uploader.
>
> The interface could be something like this:
>
> git-download-archive <repo> <git-archive-tree options...>
> git-upload-archive <directory>
>
> Or, if the big number of git command names is a concern:
>
I think it is, IMHO. And that's why I think we could have only one
command for building localy/remotely archive whatever the format.
git-archive should be a main procelain command, and we should get rid
of git-{tar,zip}-tree commands.
--
Franck
--
VGER BF report: U 0.742177
next prev parent reply other threads:[~2006-09-02 20:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 12:23 [PATCH][RFC] Add git-archive-tree Rene Scharfe
2006-09-02 12:37 ` [PATCH] Add support for tgz archive format Rene Scharfe
2006-09-02 13:10 ` [PATCH][RFC] Add git-archive-tree Rene Scharfe
2006-09-02 20:13 ` Franck Bui-Huu [this message]
2006-09-04 18:22 ` Rene Scharfe
2006-09-04 20:09 ` Junio C Hamano
2006-09-04 22:02 ` Rene Scharfe
2006-09-04 22:20 ` Junio C Hamano
2006-09-05 11:43 ` Franck Bui-Huu
2006-09-02 21:19 ` Junio C Hamano
2006-09-02 14:17 ` Rene Scharfe
2006-09-02 15:24 ` Franck Bui-Huu
2006-09-02 16:08 ` Rene Scharfe
2006-09-02 21:27 ` Junio C Hamano
2006-09-06 18:05 ` Rene Scharfe
2006-09-06 21:47 ` Junio C Hamano
2006-09-17 11:54 ` Rene Scharfe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cda58cb80609021313p5156a14du4895e53387dd24dc@mail.gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=rene.scharfe@lsrfire.ath.cx \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).