git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Stephen Bash <bash@genarts.com>
Cc: git discussion list <git@vger.kernel.org>
Subject: Re: Passing commit IDs to git-archive
Date: Sat, 10 Mar 2012 07:40:23 +0100	[thread overview]
Message-ID: <4F5AF757.2040000@lsrfire.ath.cx> (raw)
In-Reply-To: <8fb14091-99dc-4383-9cab-5bf508e0a554@mail>

Am 09.03.2012 23:14, schrieb Stephen Bash:
> Unfortunately I just attempted
>
>    warp:bar bash$ git archive --remote=file:///Users/bash/Development/foo \
>                               --output=test.tgz 3b9e49b \
>                               path/to/subdir
>    remote: fatal: no such ref: 3b9e49b
>    remote: git upload-archive: archiver died with error
>    fatal: sent error to the client: git upload-archive: archiver died with error

How about something like this instead?

	$ (
		cd /Users/bash/Development/foo &&
		git archive --format=tgz 3b9e49b path/to/subdir
	) >test.tgz

I.e. instead of using the --remote option, going to the target and 
creating the archive locally.  You could also keep using the --output 
parameter if you specify the target file using an absolute path, of course.

René

  parent reply	other threads:[~2012-03-10  6:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8c6d921d-9e8e-4caf-bc04-b1d2cfdd294f@mail>
2012-03-09 22:14 ` Passing commit IDs to git-archive Stephen Bash
2012-03-09 22:34   ` Junio C Hamano
2012-03-10  6:40   ` René Scharfe [this message]
2012-03-12 11:47   ` Jeff King
2012-03-12 13:24     ` Stephen Bash

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=4F5AF757.2040000@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=bash@genarts.com \
    --cc=git@vger.kernel.org \
    /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).