From: Matt Wette <matthew.wette@verizon.net>
To: 18477@debbugs.gnu.org
Subject: bug#18477: byte-compiled files have wrong permissions
Date: Tue, 09 Feb 2016 17:39:14 -0800 [thread overview]
Message-ID: <450F0463-33DE-4995-8AB0-28F6A044E5B7@verizon.net> (raw)
In-Reply-To: <87k355yjic.fsf@trouble.defaultvalue.org>
Comment:
Does a fix of this bug imply that permissions on each directory in the trail to compiled files should reflect the permissions on the trail to the source file?
next prev parent reply other threads:[~2016-02-10 1:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8208031408792652@web8g.yandex.ru>
2014-09-14 21:33 ` bug#18477: Bug#758971: byte-compiled files have wrong permissions Rob Browning
2016-02-10 1:39 ` Matt Wette [this message]
2016-06-21 16:06 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=450F0463-33DE-4995-8AB0-28F6A044E5B7@verizon.net \
--to=matthew.wette@verizon.net \
--cc=18477@debbugs.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).