git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Git Mailing List <git@vger.kernel.org>
Cc: Junio C Hamano <junkio@cox.net>, Franck Bui-Huu <vagabon.xyz@gmail.com>
Subject: Re: [PATCH][RFC] Add git-archive-tree
Date: Sat, 02 Sep 2006 15:10:21 +0200	[thread overview]
Message-ID: <44F982BD.1050509@lsrfire.ath.cx> (raw)
In-Reply-To: <44F977C0.4060901@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
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?

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:

   git-archive-remote --upload|--download ...

What do you all think?

I won't have time for any of this over the next few days, so Franck, go
wild. ;-)

René

-- 
VGER BF report: U 0.499999

  parent reply	other threads:[~2006-09-02 13:10 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 ` Rene Scharfe [this message]
2006-09-02 20:13   ` [PATCH][RFC] Add git-archive-tree Franck Bui-Huu
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=44F982BD.1050509@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=vagabon.xyz@gmail.com \
    /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).