From: Manuel Strehl <manuel.strehl@physik.uni-regensburg.de>
To: git@vger.kernel.org
Subject: Checking out messes up execution bit
Date: Sat, 06 Nov 2010 22:11:20 +0100 [thread overview]
Message-ID: <4CD5C478.1010604@physik.uni-regensburg.de> (raw)
Hello list,
I asked a question over at superuser.com about git checkouts messing up
the execution bit of freshly committed files:
http://superuser.com/questions/204757
To put it in a nutshell: I edit and commit a file in branch "master",
then I check out branch "dev" and the edited file gets the execution bit
set. This leads to a working copy differing from the content of the
index. It's especially painful when I try to merge "master" into "dev",
which fails then. I'm working under ext4 and Samba/CIFS, respectively.
One answerer at superuser thinks that this looks like a bug in git
itself. Therefore I'd like to check with you, if there is possibly
another explanation for my observation, before I issue a bug report.
Best,
Manuel
next reply other threads:[~2010-11-06 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 21:11 Manuel Strehl [this message]
2010-11-07 0:11 ` Checking out messes up execution bit Peter Harris
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=4CD5C478.1010604@physik.uni-regensburg.de \
--to=manuel.strehl@physik.uni-regensburg.de \
--cc=git@vger.kernel.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).