From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Re: Seeing various mode changes on cygwin
Date: Sat, 08 Oct 2005 11:51:55 -0700 [thread overview]
Message-ID: <7vfyrbrgdw.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051008180023.GC28875@diku.dk> (Jonas Fonseca's message of "Sat, 8 Oct 2005 20:00:23 +0200")
Jonas Fonseca <fonseca@diku.dk> writes:
> ... 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.
next prev parent reply other threads:[~2005-10-08 18:52 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 [this message]
2005-10-08 21:36 ` Alex Riesen
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=7vfyrbrgdw.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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).