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 23:48:10 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708062346120.14781@racer.site> (raw)
In-Reply-To: <a1bbc6950708061532t45fb0cf4w716971260b0640ae@mail.gmail.com>
Hi,
On Mon, 6 Aug 2007, Dmitry Kakurin wrote:
> On 8/6/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>
> > > Does it mean that fork of a fork does not work on repo.or.cz?
> >
> > Yes, at the moment it does not work. Therefore I set up
> > git/mingw4msysgit.git, for the time being.
>
> That's too bad. I was thinking about adopting distributed dev model for
> MinGW port of Git: we all would fork off mingw.git on repo.or.cz and
> then we would pull from each other instead of exchanging patches thru
> e-mail. Personally I don't like email patch exchange process.
We can still do that. Just set up a fork of _git.git_, and initialise it
with mingw4msysgit.git.
> Can this problem on repo.or.cs be fixed? Did Petr reply?
I think it can. But Pasky seems to be extraordinarily busy these days.
So no, I got no reply besides a message on IRC that he'll try to do
something about the situation tonight.
Ciao,
Dscho
prev parent reply other threads:[~2007-08-06 22:48 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
2007-08-06 21:56 ` Johannes Schindelin
2007-08-06 22:32 ` Dmitry Kakurin
2007-08-06 22:48 ` 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.0708062346120.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).