From: Johannes Sixt <j.sixt@viscovery.net>
To: Jussi Peltonen <peltoju@gmail.com>, git@vger.kernel.org
Subject: Re: Git clone gives zero file permissions
Date: Thu, 24 Apr 2014 12:18:49 +0200 [thread overview]
Message-ID: <5358E509.7070306@viscovery.net> (raw)
In-Reply-To: <CACDOErWqjihSYi4r6r8cjfFcbWe+7H0Tihjmkn18Y-szn7cE2g@mail.gmail.com>
Am 4/24/2014 10:24, schrieb Jussi Peltonen:
> I installed git to my Windows 7 workstation and cloned
> "http://git.ipxe.org/ipxe.git" by using the Git GUI.
>
> ipxe-23042014/src tree looks like this in Cygwin bash:
>
> Files have no permissions, same goes with subfolders, e.g.
>
> $ ls -l config/
> total 47
> ----------+ 1 peltoju Domain Users 699 Apr 23 09:00 colour.h
> ...
If that's the only problem, then I'd say: don't use Cygwin's ls to look at
these files ;-)
So, really, what is the problem? You are using:
> git-gui version 0.19.GITGUI
> git version 1.9.0.msysgit.0
This doesn't look like Cygwin's git. That there are some discrepancies in
the result produced by Git for Windows is not surprising (but I'm not
saying "is expected").
-- Hannes
prev parent reply other threads:[~2014-04-24 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 8:24 Git clone gives zero file permissions Jussi Peltonen
2014-04-24 10:18 ` Johannes Sixt [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=5358E509.7070306@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=peltoju@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).