From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: Re: MinGW port updated, now self-hosting again
Date: Tue, 13 Mar 2007 11:14:17 +0100 [thread overview]
Message-ID: <45F67979.498A321F@eudaptics.com> (raw)
In-Reply-To: 45F675E8.2E4B58B4@eudaptics.com
Johannes Sixt wrote:
>
> I've updated the MinGW port at
>
> pull/clone: git://repo.or.cz/git/mingw.git
> gitweb: http://repo.or.cz/w/git/mingw.git
>
> Thanks to the recent additions of fake symlink support, this version is
> now self-hosting on Windows again.
I forgot to mention: To make the repository self-hosting, you must set
git config core.symlinks false
but since you can do this only after a repository exists, a 'git clone'
will still fail during the checkout phase. To fix up the failure, just
enter the repository, set core.symlinks false, and follow-up with a 'git
reset --hard'.
-- Hannes
prev parent reply other threads:[~2007-03-13 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 9:59 MinGW port updated, now self-hosting again Johannes Sixt
2007-03-13 10:14 ` 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=45F67979.498A321F@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).