git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Martin Waitz <tali@admingilde.org>, Andreas Ericsson <ae@op5.se>,
	git@vger.kernel.org
Subject: Re: [PATCH] git-init: don't base core.filemode on the ability to chmod.
Date: Thu, 4 Oct 2007 13:49:43 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710041345280.4174@racer.site> (raw)
In-Reply-To: <7vir5nb89d.fsf@gitster.siamese.dyndns.org>

Hi,

On Thu, 4 Oct 2007, Junio C Hamano wrote:

> I do not think git on Cygwin nor WinGit creates $GIT_DIR/config with 
> executable bit set.  Is this pretty much a workaround only for 
> vfat-on-Linux ?

I do not know precisely about Cygwin (a quick test on my USB stick shows 
that .git/config is created without the executable bit set), but in MSys 
plain files which start with a she-bang are automatically +x, while all 
other plain files are automatically -x (therefore this applies to 
.git/config).

Given these findings, I fail to see what the patch should achieve, as 
the first test (for -x) always succeeds...

Ciao,
Dscho

  parent reply	other threads:[~2007-10-04 12:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03 10:55 [PATCH] git-init: don't base core.filemode on the ability to chmod Martin Waitz
2007-10-03 12:19 ` Johannes Sixt
2007-10-03 23:19   ` Martin Waitz
2007-10-03 23:54     ` Johannes Schindelin
2007-10-04  6:05       ` Andreas Ericsson
2007-10-04  6:23         ` Junio C Hamano
2007-10-04  7:17           ` Martin Waitz
2007-10-04  8:21             ` Junio C Hamano
2007-10-04  8:36               ` Johannes Sixt
2007-10-04  8:42               ` Martin Waitz
2007-10-10  9:47                 ` Jan Hudec
2007-10-04 12:49               ` Johannes Schindelin [this message]
2007-10-04 10:33           ` Andreas Ericsson
2007-10-04  7:15       ` Martin Waitz

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=Pine.LNX.4.64.0710041345280.4174@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=tali@admingilde.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 NNTP newsgroup(s).