git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH V2B] core.filemode may need manual action
Date: Sun, 19 Oct 2014 15:37:53 -0700	[thread overview]
Message-ID: <xmqqmw8rr8hq.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <54418CC7.80601@web.de> ("Torsten Bögershausen"'s message of "Fri, 17 Oct 2014 23:40:23 +0200")

Torsten Bögershausen <tboegi@web.de> writes:

> Does this makes more sence ?

Giving the links in-line in the text and avoiding to repeat the same
information at the end like this version does probably makes sense.
Good thinking.

Thanks.

>
>  Documentation/config.txt | 23 ++++++++++++++++++-----
>  1 file changed, 18 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index 04a1e2f..3127e5d 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -204,13 +204,26 @@ advice.*::
>  --
>  
>  core.fileMode::
> -	If false, the executable bit differences between the index and
> -	the working tree are ignored; useful on broken filesystems like FAT.
> +	Tells Git if the executable bit of files in the working tree
> +	is to be honored.
> ++
> +	Some filesystems lose the executable bit when a file that is
> +	marked as executable is checked out, or checks out an
> +	non-executable file with executable bit on.
> +	linkgit:git-clone[1] or linkgit:git-init[1] probe the filesystem
> +	to see if it handles the executable bit correctly
> +	and this variable is automatically set as necessary.
> ++
> +	A repository, however, may be on a filesystem that handles
> +	the filemode correctly, and this variable is set to 'true'
> +	when created, but later may be made accessible from another
> +	environment that loses the filemode (e.g. exporting ext4 via
> +	CIFS mount, visiting a Cygwin created repository with
> +	Git for Windows or Eclipse).
> +	In such a case it may be necessary to set this variable to 'false'.
>  	See linkgit:git-update-index[1].
>  +
> -The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
> -will probe and set core.fileMode false if appropriate when the
> -repository is created.
> +The default is true (when core.filemode is not specified in the config file).
>  
>  core.ignorecase::
>  	If true, this option enables various workarounds to enable

      reply	other threads:[~2014-10-19 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 21:40 [PATCH V2B] core.filemode may need manual action Torsten Bögershausen
2014-10-19 22:37 ` Junio C Hamano [this message]

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=xmqqmw8rr8hq.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=tboegi@web.de \
    /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).