From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: MinGW port updated to GIT 1.5.0
Date: Thu, 15 Feb 2007 13:19:33 +0100 [thread overview]
Message-ID: <45D44FD5.72299A3A@eudaptics.com> (raw)
I've merged GIT 1.5.0 into the MinGW port. It is available at the usual
location:
pull/clone: git://repo.or.cz/git/mingw.git
gitweb: http://repo.or.cz/w/git/mingw.git
It contains an important fix (MinGW specific): Earlier versions could
sometimes create temporary files read-only instead of read-writable.
WARNING!
The MinGW port does not support symbolic links, but the git.git itself
now contains a symbolic link (RelNotes). For this reason, you cannot
successfully pull this version's "master" branch to your Windows box and
expect it to work. The "devel" branch has the symbolic link removed, so
it can at least be checked out. For other operations you may enounter an
error like this:
bad tree object: 4571d0d1cfb5a4170dfc80e9654228acae295129
I'm working on a solution. The general idea is to extend the meaning of
`core.filemode = false` to check out symbolic links as plain files. Any
hints about where the source code needs changes are welcome.
-- Hannes
next reply other threads:[~2007-02-15 12:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 12:19 Johannes Sixt [this message]
2007-02-15 16:53 ` GIT 1.5.0 binary installer available Han-Wen Nienhuys
2007-02-15 19:11 ` Johannes Schindelin
2007-02-15 19:52 ` Johannes Schindelin
2007-02-15 20:12 ` Shawn O. Pearce
2007-02-16 4:23 ` Johannes Schindelin
2007-02-16 5:06 ` Shawn O. Pearce
2007-02-16 19:10 ` Marco Costalba
2007-02-15 17:43 ` MinGW port updated to GIT 1.5.0 Junio C Hamano
2007-02-15 18:59 ` Junio C Hamano
2007-02-15 19:14 ` Johannes Schindelin
2007-02-15 19:41 ` Robin Rosenberg
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=45D44FD5.72299A3A@eudaptics.com \
--to=j.sixt@eudaptics.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;
as well as URLs for NNTP newsgroup(s).