From: "Dmitry Kakurin" <dmitry.kakurin@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
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 14:55:09 -0700 [thread overview]
Message-ID: <a1bbc6950708061455v459182cei3fb6b3b518d4b176@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708061134380.14781@racer.site>
On 8/6/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 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.
Does it mean that fork of a fork does not work on repo.or.cz?
- Dmitry
next prev parent reply other threads:[~2007-08-06 21:55 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
2007-08-06 21:51 ` Dmitry Kakurin
2007-08-06 21:55 ` Dmitry Kakurin [this message]
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=a1bbc6950708061455v459182cei3fb6b3b518d4b176@mail.gmail.com \
--to=dmitry.kakurin@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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).