From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Dmitry Kakurin <dmitry.kakurin@gmail.com>
Cc: git@vger.kernel.org, johannes.sixt@telecom.at
Subject: Re: [MinGW PATCH] 'git clone git://...' was failing inside git-read-tree with 'fatal: Not a valid object name HEAD'
Date: Sat, 4 Aug 2007 15:16:28 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708041515251.14781@racer.site> (raw)
In-Reply-To: <F7C35F51E58245FDA1EE1C2F2B4EB204@ntdev.corp.microsoft.com>
Hi,
On Sat, 4 Aug 2007, Dmitry Kakurin wrote:
> NOTE: This fix uses is_absolute_path from msysGit-0.3.exe that is not in
> mingw.git yet.
Ooops. I think I did not even check that into msysgit.git. Thanks.
> - if (gitdirenv[0] != '/') {
> + if ( !is_absolute_path( gitdirenv ) ) {
Our coding style does not want them extra spaces...
+ if (!is_absolute_path(gitdirenv)) {
is the way we prefer it.
Ciao,
Dscho
prev parent reply other threads:[~2007-08-04 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 11:38 [MinGW PATCH] 'git clone git://...' was failing inside git-read-tree with 'fatal: Not a valid object name HEAD' Dmitry Kakurin
2007-08-04 14:16 ` Johannes Schindelin [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=Pine.LNX.4.64.0708041515251.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=dmitry.kakurin@gmail.com \
--cc=git@vger.kernel.org \
--cc=johannes.sixt@telecom.at \
/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).