All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Dmitry Oksenchuk <oksenchuk89@gmail.com>, git <git@vger.kernel.org>
Subject: Re: git merge changes file mode from 644 to 755
Date: Fri, 14 Aug 2015 16:17:53 +0200	[thread overview]
Message-ID: <55CDF891.4080709@kdbg.org> (raw)
In-Reply-To: <CA+POfmsohJAGVYHM3nHJydoyxe92QFd59eWT_UG+_0fM46SATA@mail.gmail.com>

Am 14.08.2015 um 14:02 schrieb Dmitry Oksenchuk:
> Hello,
>
> I've noticed strange behavior of git merge on Windows with
> core.filemode=false (set by default). Git changed mode of some files
> from 644 to 755 for unknown reason. One of the files is stdafx.cpp,
> it's absent in the common ancestor, it was added in the first branch
> (master) with mode 644 and it's still absent in the second branch
> (feature). So, git merges the file without conflicts but changes mode
> from 644 to 755.

I do know the git-merge-recursive does not honor core.filemode. However, 
I am surprised to see a mode change from 644 to 755. I usually observe 
only mode changes from 755 to 644, but then the case where the file is 
not present on one branch is uncommon for me.

> Why git merge changes mode from 644 to 755? Is it a known issue?

So, well, yes, it is known that with git merge mode changes do occur, 
but no, 644 to 755 is news to me.

The work-around is to unstage the file and stage it again, e.g. with 
git-gui and then to amend the merge commit.

-- Hannes

      reply	other threads:[~2015-08-14 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 12:02 git merge changes file mode from 644 to 755 Dmitry Oksenchuk
2015-08-14 14:17 ` Johannes Sixt [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=55CDF891.4080709@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=git@vger.kernel.org \
    --cc=oksenchuk89@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.