From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christoph Anton Mitterer <calestyo@scientia.net>, git@vger.kernel.org
Subject: Re: [cosmetic bug?] needlessly(?) executable files
Date: Mon, 23 Feb 2015 09:21:03 +0100 [thread overview]
Message-ID: <1424679663.30155.30.camel@kaarsemaker.net> (raw)
In-Reply-To: <xmqqr3thwzur.fsf@gitster.dls.corp.google.com>
On zo, 2015-02-22 at 10:44 -0800, Junio C Hamano wrote:
> Christoph Anton Mitterer <calestyo@scientia.net> writes:
>
> > Just a question about files like:
> > .git/config
> > .git/hooks/*.sample
> >
> > Is there any reason that these are created executable? Especially
> the
> > config file?
>
> In a new repository I just did "git init", I see this:
>
> $ rm -fr stupid
> $ umask 0027
> $ git init stupid
> $ ls -l stupid/.git/config | sed -e 's/ .*//'
> -rw-r-----
>
> So no, config is not created executable.
It used to be for a brief period in history, between daa22c6f8d (2.1.0)
and 1f32ecf (2.2.2).
--
Dennis Kaarsemaker
http://www.kaarsemaker.net
next prev parent reply other threads:[~2015-02-23 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 17:48 [cosmetic bug?] needlessly(?) executable files Christoph Anton Mitterer
2015-02-22 18:44 ` Junio C Hamano
2015-02-23 8:21 ` Dennis Kaarsemaker [this message]
2015-02-23 13:08 ` Christoph Anton Mitterer
2015-02-23 18:55 ` 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=1424679663.30155.30.camel@kaarsemaker.net \
--to=dennis@kaarsemaker.net \
--cc=calestyo@scientia.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 NNTP newsgroup(s).