git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Johannes Sixt <J.Sixt@eudaptics.com>, git@vger.kernel.org
Subject: Re: most commonly used git commands?
Date: Sun, 1 Jul 2007 00:35:04 +0200	[thread overview]
Message-ID: <20070630223504.GB2703@steel.home> (raw)
In-Reply-To: <Pine.LNX.4.64.0706301531050.4438@racer.site>

Johannes Schindelin, Sat, Jun 30, 2007 16:31:48 +0200:
> On Sat, 30 Jun 2007, Alex Riesen wrote:
> > Johannes Schindelin, Thu, Jun 28, 2007 16:07:17 +0200:
> > > > No. It was meant as Alex said it. Windows (MinGW) doesn't understand
> > > > "chmod a+x blub".
> > > 
> > > Yes, I suspected that. But I don't see a need for it on Windows (MinGW) to 
> > > begin with.
> > > 
> > 
> > But it is necessary on Windows (Cygwin):
> 
> I thought that on Cygwin, filemode=1? I mean, Cygwin _never_ had problems 
> with chmod under my fingers.
> 

Try doing stat(2) on file.txt which contains "#!/bin/sh" in its first
line and for which you have issued a chmod yet. Like a new file, or
like every file in a git-tracked directory after you did a fresh
checkout. Cygwin actually opens the files when doing stat(2), looks
inside and tries to guess if they are executable.

You should have said: "Cygwin _never_ had problems with chmod because
it cannot and didn't make it work". It is not just chmod, the other
side, stat, matters as well.

  reply	other threads:[~2007-06-30 22:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25  6:40 most commonly used git commands? Michael S. Tsirkin
2007-06-25  7:10 ` Junio C Hamano
2007-06-25  7:17   ` Michael S. Tsirkin
2007-06-25  7:48     ` Junio C Hamano
2007-06-28  2:17       ` Martin Langhoff
2007-06-28  2:30         ` Josh Triplett
2007-06-25  7:51     ` Johannes Schindelin
2007-06-28  8:52       ` Alex Riesen
2007-06-28 13:08         ` Johannes Schindelin
2007-06-28 13:54           ` Johannes Sixt
2007-06-28 14:07             ` Johannes Schindelin
2007-06-28 14:29               ` Johannes Sixt
2007-06-28 14:49                 ` Johannes Sixt
2007-06-28 17:02                   ` [PATCH] git add: respect core.filemode even with unmerged entries in the index Johannes Schindelin
2007-06-29  6:57                     ` [PATCH] git add: respect core.filemode even with unmerged entriesin " Johannes Sixt
2007-06-29 10:07                       ` Johannes Schindelin
2007-06-29 10:20                         ` Junio C Hamano
2007-06-29 17:32                           ` [PATCH] git add: respect core.filemode with unmerged entries Johannes Schindelin
2007-06-29  8:36                     ` [PATCH] git add: respect core.filemode even with unmerged entries in the index Junio C Hamano
2007-06-29 10:06                       ` Johannes Schindelin
2007-06-30 13:14               ` most commonly used git commands? Alex Riesen
2007-06-30 14:31                 ` Johannes Schindelin
2007-06-30 22:35                   ` Alex Riesen [this message]
2007-07-01  9:16                     ` Jan Hudec
2007-07-01 16:49                       ` Alex Riesen
2007-06-28  1:37 ` Josh Triplett

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=20070630223504.GB2703@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=J.Sixt@eudaptics.com \
    --cc=Johannes.Schindelin@gmx.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).