From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Dmitry Kakurin <dmitry.kakurin@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [MinGW PATCH] git clone was failing with 'invalid object name HEAD' if ran from cmd.exe directly
Date: Mon, 6 Aug 2007 11:42:42 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708061134380.14781@racer.site> (raw)
In-Reply-To: <BD28FA320B7749FFBE3135FE92380BCE@ntdev.corp.microsoft.com>
Hi,
On Mon, 6 Aug 2007, Dmitry Kakurin wrote:
> environment.c caches results of many getenv calls. Under MinGW setenv(X)
> invalidates all previous values returned by getenv(X) so cached values
> become dangling pointers.
>
> Added cache-aware function set_git_dir to complement get_git_dir
The real problem here: mingw.git did not merge with upstream git.git in a
long time (mainly because its maintainer is on holiday). In the meantime,
set_git_dir() is already there!
I had more problems than I thought with setting up a fork of mingw.git.
It seems that the relative alternates path to mingw.git is followed, but
not that one from mingw.git to git.git. So I could upload, but not fetch.
So I propose to use http://repo.or.cz/w/git/mingw4msysgit.git/ in the
meantime. (Just give me your account name, and you'll be able to push to
it.)
BTW your patch was white-space mangled.
Ciao,
Dscho
next prev parent reply other threads:[~2007-08-06 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 9:44 [MinGW PATCH] git clone was failing with 'invalid object name HEAD' if ran from cmd.exe directly Dmitry Kakurin
2007-08-06 10:42 ` Johannes Schindelin [this message]
2007-08-06 21:51 ` Dmitry Kakurin
2007-08-06 21:55 ` Dmitry Kakurin
2007-08-06 21:56 ` Johannes Schindelin
2007-08-06 22:32 ` Dmitry Kakurin
2007-08-06 22:48 ` Johannes Schindelin
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=Pine.LNX.4.64.0708061134380.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=dmitry.kakurin@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;
as well as URLs for NNTP newsgroup(s).