public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Kaz Kylheku <920-082-4242@kylheku.com>
To: cygwin@cygwin.com
Subject: Re: Request to the git maintainer
Date: Mon, 10 Jul 2017 22:27:00 -0000	[thread overview]
Message-ID: <5b9b894856c27a28ce349b3689fe8751@mail.kylheku.com> (raw)
In-Reply-To: <64cc57cf-09c7-6225-963f-9adacb7d03af@cs.umass.edu>

On 10.07.2017 14:02, Eliot Moss wrote:
> On 7/10/2017 4:24 PM, Achim Gratz wrote:
>> Eliot Moss writes:
>>> 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.
>> 
>> That's an upstream build system bug.  Some of the installation scripts
>> use cp instead of install and that in turn makes them dependent on 
>> umask
>> (which doesn't get set aywhere I can easily find).  I guess Adam could
>> work around that by setting 'umask 022' in the cygport file, but it
>> really should be fixed in git.git.
> 
> I looked upstream, and at least some of the files I am concerned about
> are installed using "tar" piped to another "tar", with umask 022 set
> explicitly.  I think the problem is that the source of this copying
> has 600 or 700 permissions.  Not sure if *that* is an upstream problem
> or not ...

I would say, get a backup system that handles whatever bits you have
on your disk, or find out how to configure the existing one.

If there are some permission problems, maybe it needs more privilege
to do its job.

You can't ask every vendor of everything that you have installed
or "git pulled" to fix their permissions because your backup program
has bizarre limitations.



--
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

  reply	other threads:[~2017-07-10 22:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07 18:23 Eliot Moss
2017-07-10 20:24 ` Achim Gratz
2017-07-10 20:45   ` Eliot Moss
2017-07-10 21:02   ` Eliot Moss
2017-07-10 22:27     ` Kaz Kylheku [this message]
2017-07-10 23:17       ` Eliot Moss
2017-07-10 23:49         ` Erik Soderquist
2017-07-11  1:38         ` Brian Inglis
2017-07-11  2:00           ` Eliot Moss
2017-07-11  2:33             ` Brian Inglis
2017-07-11 12:34               ` Eliot Moss
2017-07-11 16:34                 ` Eliot Moss
2017-07-11 20:35     ` Achim Gratz

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=5b9b894856c27a28ce349b3689fe8751@mail.kylheku.com \
    --to=920-082-4242@kylheku.com \
    --cc=cygwin@cygwin.com \
    /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).