git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: git-list <git@vger.kernel.org>
Subject: Re: git-tar-tree & NEEDS_PREFIX
Date: Sun, 08 Oct 2006 15:44:32 +0200	[thread overview]
Message-ID: <452900C0.6090406@lsrfire.ath.cx> (raw)
In-Reply-To: <4528F8AD.2040307@gmail.com>

Jiri Slaby schrieb:
> is there any good reason to have NEEDS_PREFIX flag for git-tar-tree
> builtin?
> 
> I can't do --remote= tar-ing, but when I remove this flag from git.c, it
> seems to work correctly (prefix seems not to be used in any way).

Good point.  However, git-tar-tree has been deprecated in favour of
git-archive.  And NEEDS_PREFIX has been renamed to RUN_SETUP two months
ago, so an update might be in order. ;-)

René

  reply	other threads:[~2006-10-08 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-08 13:10 git-tar-tree & NEEDS_PREFIX Jiri Slaby
2006-10-08 13:44 ` Rene Scharfe [this message]
2006-10-08 13:44 ` [PATCH] git-tar-tree: don't RUN_SETUP 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=452900C0.6090406@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=git@vger.kernel.org \
    --cc=jirislaby@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).