DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:to:from:subject:message-id:date
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=n/GP4QdmhO6FY1Bh7umGycU66975A7kBnv41R9iRD/7afbdLerN4w
	HGDRQB7k2fbg3oqa3oOQ+M7TFbIRkcBQf0woey1Y5oAXOkuMOA4+AoXRginBLaZt
	JGDcsgFQjsxQ4n58PAvbmC+7t8l48DJ42LiDpNmcmm9GIsMcrZxa9Q=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Reply-To: moss AT cs DOT umass DOT edu
To: cygwin <cygwin AT cygwin DOT com>
From: Eliot Moss <moss AT cs DOT umass DOT edu>
Subject: Request to the git maintainer
Message-ID: <b5a70575-b81b-12c1-aad3-b100dd7acaa0@cs.umass.edu>
Date: Fri, 7 Jul 2017 14:23:02 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Dear maintainer of git ....

I use CrashPlan as my backup engine.  It has difficulty backing up
files with no "other" access.  Many git locale (.mo) and doc-related
files have permissions 600 (directories 700).  Is there a good reason
for this?  I would think that 644 and 755 access would be fine for
these files, and it would prevent the problems I see with CrashPlan.

For the moment I have changed the access modes locally, but I suspect
that future updates will cause reversion unless this is fixed upstream.

(If there are other files out there in the Cygwin universe whose
"other" access is denied for no good reason, I would ask the same
for them :-) ...)

Regards - Eliot Moss

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple