git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Sun, 9 Oct 2005 15:02:53 +0200	[thread overview]
Message-ID: <20051009130253.GA14237@steel.home> (raw)
In-Reply-To: <7vzmpjoa32.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano, Sun, Oct 09, 2005 01:36:17 +0200:
> > These are not real attributes, cygwin emulates them from the names,
> > like .exe will always be 0755, for example.
> 
> Ouch.  Is this true in general, or only on FAT-derived
> filesystems?
> 

Before they are chmod'ed by cygwin (with chmod): probably everywhere
on windows (I'm sure about vfat, were chmod wont help at all).  Even
if you can save user (unix) attributes somewhere, initial clone will
still always have this problem.

      parent reply	other threads:[~2005-10-09 13:03 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
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 [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=20051009130253.GA14237@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).