From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Yann Simon <yann.simon.fr@gmail.com>, git <git@vger.kernel.org>
Subject: Re: [PATCH JGIT] Compute the author/commiter name and email from the git configuration
Date: Wed, 4 Feb 2009 02:04:15 +0100 [thread overview]
Message-ID: <200902040204.16102.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <20090204005907.GA23383@spearce.org>
onsdag 04 februari 2009 01:59:07 skrev Shawn O. Pearce:
> Hell, Java 6 added an executable flag to java.io.File. This is
> a rather funny concept on Windows where executablity is based on
> file name and not a "mode bit", but its in the Java 6 S2SE API.
> At least even on Windows getenv makes sense and provides data.
There is an execute bit in windows ACL's. Disable it for an executables (exe, dll etc and
see for yourself). I've hit it when trying to track an eclipse installation using git and
some DLL wasn't executable after a checkout.
-- robin
next prev parent reply other threads:[~2009-02-04 1:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 21:13 [PATCH JGIT] Compute the author/commiter name and email from the git configuration Yann Simon
2009-02-03 23:13 ` Shawn O. Pearce
2009-02-03 23:20 ` Johannes Schindelin
2009-02-04 0:55 ` Robin Rosenberg
2009-02-04 1:01 ` Shawn O. Pearce
2009-02-04 0:59 ` Shawn O. Pearce
2009-02-04 1:04 ` Robin Rosenberg [this message]
2009-02-04 8:14 ` Yann Simon
2009-02-04 8:42 ` Yann Simon
2009-02-04 8:08 ` Yann Simon
-- strict thread matches above, loose matches on Subject: below --
2009-02-04 12:28 Yann Simon
2009-02-04 17:36 ` Shawn O. Pearce
2009-02-05 9:27 Yann Simon
2009-02-05 10:44 Yann Simon
2009-02-05 15:38 ` Shawn O. Pearce
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=200902040204.16102.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=yann.simon.fr@gmail.com \
/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).