From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Jeff King <peff@peff.net>
Cc: Neal Kreitzinger <neal@rsss.com>, git@vger.kernel.org
Subject: Re: git-archive and tar options
Date: Thu, 14 Jul 2011 19:16:24 +0200 [thread overview]
Message-ID: <4E1F2468.6080409@lsrfire.ath.cx> (raw)
In-Reply-To: <20110714015656.GA20136@sigill.intra.peff.net>
Am 14.07.2011 03:56, schrieb Jeff King:
> On Wed, Jul 13, 2011 at 06:34:32PM -0500, Neal Kreitzinger wrote:
>> Working syntax starting points for git-archive and tar:
>>
>> git archive --format=tar -o my.tar HEAD Web/Templates/
>> tar -cvf my.tar --transform 's,^Web/Templates/,myPath/myWeb/Templates/,'
>> WebPortal/Templates/
>>
>> Failed syntax attempts for feeding tar option to git-archive:
>>
>> git archive --format=tar -o my.tar HEAD --transform
>> 's,^Web/Templates/,myPath/myWeb/Templates/,' WebPortal/Templates/
>> error: unknown option `transform'
>>
>> git archive --format=tar -o my.tar --transform
>> 's,^Web/Templates/,myPath/myWeb/Templates/,' HEAD WebPortal/Templates/
>> error: unknown option `transform'
>
> Yeah, that won't work, because there is no such option. We do have
> "--prefix", but I suspect that's not flexible enough for what you want.
If you only need a single subdirectory with a custom prefix you could do
something like this (variables only used to keep the lines short):
$ subdir=WebPortal/Templates
$ prefix=myPath/myWeb/Templates/
$ (cd "$subdir" && git archive --prefix="$prefix" HEAD) >my.tar
The output file can be specified with -o as well, of course, but you'd
either need to use an absolute path or add "../" for each directory
level you descend into (-o ../../my.tar in this case).
René
next prev parent reply other threads:[~2011-07-14 17:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 23:34 git-archive and tar options Neal Kreitzinger
2011-07-14 1:56 ` Jeff King
2011-07-14 17:16 ` René Scharfe [this message]
2011-07-14 17:27 ` Jeff King
2011-07-14 17:45 ` René Scharfe
2011-07-14 18:18 ` Jeff King
2011-07-14 19:12 ` Jakub Narebski
2011-07-14 21:23 ` Junio C Hamano
2011-07-14 21:25 ` Jeff King
2011-07-14 23:30 ` Junio C Hamano
2011-07-15 20:59 ` René Scharfe
2011-07-18 19:31 ` Neal Kreitzinger
2011-07-18 20:50 ` René Scharfe
2011-07-14 21:38 ` Jakub Narebski
2011-07-18 18:13 ` Neal Kreitzinger
2011-07-18 20:50 ` René Scharfe
2011-07-19 0:12 ` Neal Kreitzinger
2011-07-19 17:56 ` René Scharfe
2011-07-21 2:13 ` Neal Kreitzinger
2011-07-21 16:59 ` Neal Kreitzinger
2011-07-14 17:48 ` Andreas Schwab
2011-07-19 20:10 ` Sylvain Rabot
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=4E1F2468.6080409@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=neal@rsss.com \
--cc=peff@peff.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.