From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git on cygwin
Date: Sat, 25 Nov 2006 15:58:51 +0100 [thread overview]
Message-ID: <ek9lkc$ahf$1@sea.gmane.org> (raw)
In-Reply-To: 4568555F.8050500@byu.net
Eric Blake wrote:
> I found the following patch useful for building git 1.4.4.1 on cygwin. As
> of cygwin-1.5.22, C99 format strings are now supported (since I
> contributed the newlib patch that added them). As of cygwin-1.5.21, d_ino
> is now reliable for all cygwin filesystem accesses (except for some remote
> NetApp drives, which have been fixed in cygwin CVS). And while it is true
> that native Windows does not support symlinks, making NO_SYMLINK_HEAD a
> good idea for native builds; this is not the case for cygwin, and I did
> not seem to have any problems with removing it, either.
By the way, does ./configure script (make configure && ./configure)
detect this correctly?
BTW. symlink HEAD is considered obsolete.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2006-11-25 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-25 14:38 git on cygwin Eric Blake
2006-11-25 14:58 ` Jakub Narebski [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='ek9lkc$ahf$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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