From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: What will happen to git.git in the near future
Date: Sun, 24 Sep 2006 18:56:07 +0200 [thread overview]
Message-ID: <4516B8A7.6010007@lsrfire.ath.cx> (raw)
In-Reply-To: <7v7iztbldm.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano schrieb:
> - We should deprecate git-tar-tree. However, it has been
> around and advertised for quite some time, so we need to make
> sure people would not get burned too badly. It might be
> worthwhile to rewrite git-tar-tree as a thin wrapper to
> "git-archive --format=tar" and remove git-upload-tar now (in
> other words, "git-tar-tree --remote" will continue to work,
> but it will talk with "git-upload-archive", not with
> "git-upload-tar" on the other end), release 1.4.3 with it
> with a deprecation warning, and then remove it in 1.4.5.
Hmm. The local case in git-tar-tree is already a thin wrapper.
How about something like this shell script as a replacement for
the entire command?
René
--- snip! --
#!/bin/sh
#
# Copyright (C) 2006 Rene Scharfe
USAGE='[--remote=<repo>] <tree-ish> [basedir]'
. git-sh-setup
case "$1" in
--remote=*) remote=1;;
*) remote=0;;
esac
case "$#,$remote" in
1,0) exec git-archive --format=tar "$1";;
2,0) exec git-archive --format=tar --prefix="$2"/ "$1";;
2,1) exec git-archive --format=tar "$1" "$2";;
3,1) exec git-archive --format=tar --prefix="$3"/ "$1" "$2";;
*) usage;;
esac
next prev parent reply other threads:[~2006-09-24 16:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 10:37 What will happen to git.git in the near future Junio C Hamano
2006-09-24 11:04 ` Petr Baudis
2006-09-24 16:56 ` Rene Scharfe [this message]
2006-09-24 18:33 ` Johannes Schindelin
2006-09-24 18:42 ` A Large Angry SCM
2006-10-01 10:16 ` Junio C Hamano
2006-10-01 18:38 ` Linus Torvalds
2006-10-01 18:47 ` Junio C Hamano
2006-10-01 19:56 ` Linus Torvalds
2006-10-01 18:53 ` Johannes Schindelin
2006-10-01 19:57 ` Linus Torvalds
2006-10-01 20:11 ` Johannes Schindelin
2006-10-01 20:23 ` Linus Torvalds
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=4516B8A7.6010007@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.