From: Matt McCutchen <hashproduct@verizon.net>
To: git@vger.kernel.org
Subject: Producing tar file with 666/777 permissions
Date: Fri, 03 Mar 2006 23:25:31 -0500 [thread overview]
Message-ID: <1141446331.3171.4.camel@mattlaptop> (raw)
Dear GIT people,
How do I package a git repository in a tar file with 666 and 777
embedded permissions? There's evidently some way to do it because the
Linux kernel source packages have 666 and 777 embedded permissions, but
git-tar-tree gives me a tar file with 644 and 755 permissions and
there's no obvious way to tell it to do otherwise.
There was lots of discussion on the mailing list about what permissions
to preserve when copying in and out of repositories (I obviously side
with those who want a single execute bit), but I could not find any
mention of permission issues in reference to git-tar-tree.
Please reply to me as I am off-list.
--
Matt McCutchen
hashproduct@verizon.net
http://hashproduct.metaesthetics.net/
next reply other threads:[~2006-03-04 4:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 4:25 Matt McCutchen [this message]
2006-03-04 5:03 ` Producing tar file with 666/777 permissions Junio C Hamano
2006-03-04 5:35 ` [PATCH] tar-tree: file/dirmode fix Junio C Hamano
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=1141446331.3171.4.camel@mattlaptop \
--to=hashproduct@verizon.net \
--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