From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Neal Kreitzinger <nkreitzinger@gmail.com>
Cc: Jeff King <peff@peff.net>, Neal Kreitzinger <neal@rsss.com>,
git@vger.kernel.org
Subject: Re: git-archive and tar options
Date: Mon, 18 Jul 2011 22:50:28 +0200 [thread overview]
Message-ID: <4E249C94.3040002@lsrfire.ath.cx> (raw)
In-Reply-To: <4E2477E1.5090406@gmail.com>
Am 18.07.2011 20:13, schrieb Neal Kreitzinger:
> HEAD:$subdir worked on my bare repo. I ran it for each transformant
> pathspec and then combined the archives with tar --catenate:
>
> # git archive --format=tar --prefix=myWeb/myRoot/myAPP/Templates/
> HEAD:WebPortal/Templates/ >myAPP.myTag.tar
> # git archive --format=tar --prefix=opt/mySTUFF/v01/SCRIPTS/
> HEAD:SCRIPTS/ >SCRIPTS.tar
> # tar --file=myAPP.myTag.tar -A SCRIPTS.tar
>
> However, the permissions also need to change to 777 and tar --mode would
> not effect this in combination with --catenation or -x. Is there a way
> I can change the permissions without having to untar->chmod->retar, and
> without having to use a non-bare repo as an intermediary?
You can use the configuration setting tar.umask to affect the
permissions of the archive entries. Set it to 0 to pass the permission
bits from the repo unchanged.
René
next prev parent reply other threads:[~2011-07-18 20:50 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
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 [this message]
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=4E249C94.3040002@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=neal@rsss.com \
--cc=nkreitzinger@gmail.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.