From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Seeing various mode changes on cygwin
Date: Sat, 8 Oct 2005 23:36:12 +0200 [thread overview]
Message-ID: <20051008213612.GA5794@steel.home> (raw)
In-Reply-To: <7vfyrbrgdw.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano, Sat, Oct 08, 2005 20:51:55 +0200:
> > ... It seems that cygwin overrides the previous modes and sets the
> > executable bit. git-reset doesn't fix it. Can this even be fixed
> > then?
> >
> > A few examples below ...
> >
> > jonas@cygwin /usr/local/dev/git/git
> > $ git reset
> > Documentation/sort_glossary.pl: needs update
> > t/lib-read-tree-m-3way.sh: needs update
>
> I do not have an access to Cygwin environment so cannot be of
> help on this directly, but 'git reset' without flags defaults
> "--mixed" and leaves the modified files intact. Maybe hard
> reset would help here, but the real solution is to figure out
> why these files acquired the extra executable bits in the first
> place.
These are not real attributes, cygwin emulates them from the names,
like .exe will always be 0755, for example.
next prev parent reply other threads:[~2005-10-08 21:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 18:00 Seeing various mode changes on cygwin Jonas Fonseca
2005-10-08 18:51 ` Junio C Hamano
2005-10-08 21:36 ` Alex Riesen [this message]
2005-10-08 23:36 ` Junio C Hamano
2005-10-09 2:19 ` Linus Torvalds
2005-10-09 6:46 ` Junio C Hamano
2005-10-10 6:48 ` Daniel Barkalow
2005-10-10 7:38 ` Junio C Hamano
2005-10-10 17:59 ` Daniel Barkalow
2005-10-10 18:22 ` Linus Torvalds
2005-10-10 21:35 ` Add ".git/config" file parser Linus Torvalds
2005-10-10 21:47 ` Linus Torvalds
2005-10-10 21:50 ` H. Peter Anvin
2005-10-10 22:12 ` Linus Torvalds
2005-10-12 0:25 ` Junio C Hamano
2005-10-12 7:43 ` [PATCH] Use core.filemode Junio C Hamano
2005-10-09 3:43 ` Seeing various mode changes on cygwin H. Peter Anvin
2005-10-09 13:02 ` Alex Riesen
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=20051008213612.GA5794@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).