public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Symbilic links support
Date: Tue, 25 Oct 2011 18:16:00 -0000	[thread overview]
Message-ID: <4EA6FCF4.7090908@redhat.com> (raw)
In-Reply-To: <CAO1Zr+of4pSyg2+8u+hZx-UqkidOdneUCWOau7yWR-YN+q30Ww@mail.gmail.com>

On 10/25/2011 11:48 AM, Alexey Kuznetsov wrote:
> By default git checkout files created as symbolic links on linux
> system as symbolic links. Under windows it does not work.
>
> I expect on cygwin machines after git checkout I will get normal links
> can be readed as 'ls -al' command. But they actually appears as normal
> files.

Does adding this to your ~/.gitconfig help?

[core]
	filemode = true

If so, we need to push back on the upstream git folks to tell them that 
their defaults on cygwin are wrong, for any repository that wants to use 
symlinks.  Upstream git is playing nasty tricks of trying to go behind 
cygwin's back, and use native windows functions instead of stat() for 
speed, but as a result of those games, they break symlink support.

I guess I should look into packaging the latest upstream git soon, 
anyways, and as part of that packaging, I'll see if I can tweak the 
default to avoid the brain-dead upstream "optimization", at least for 
out-of-the-box configuration, if that does indeed fix your problem.

-- 
Eric Blake   eblake@redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2011-10-25 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25 17:49 Alexey Kuznetsov
2011-10-25 18:16 ` Eric Blake [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=4EA6FCF4.7090908@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).