From: Junio C Hamano <junkio@cox.net>
To: Matt McCutchen <hashproduct@verizon.net>
Cc: git@vger.kernel.org
Subject: Re: Producing tar file with 666/777 permissions
Date: Fri, 03 Mar 2006 21:03:57 -0800 [thread overview]
Message-ID: <7v7j7ax0le.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1141446331.3171.4.camel@mattlaptop> (Matt McCutchen's message of "Fri, 03 Mar 2006 23:25:31 -0500")
Matt McCutchen <hashproduct@verizon.net> writes:
> 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.
Ouch, thanks for reporting this. You have spotted a recent
regression.
next prev parent reply other threads:[~2006-03-04 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 4:25 Producing tar file with 666/777 permissions Matt McCutchen
2006-03-04 5:03 ` Junio C Hamano [this message]
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=7v7j7ax0le.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=hashproduct@verizon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox