From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Abdelrazak Younes <younes.a@free.fr>,
git@vger.kernel.org, msysgit@googlegroups.com
Subject: Re: Windows binaries for qgit 2.0
Date: Mon, 17 Dec 2007 19:13:16 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0712171911070.9446@racer.site> (raw)
In-Reply-To: <e5bfff550712171105k62b90853w1c5eed64bd11fb23@mail.gmail.com>
Hi,
On Mon, 17 Dec 2007, Marco Costalba wrote:
> On Dec 17, 2007 10:51 AM, Abdelrazak Younes <younes.a@free.fr> wrote:
> >
> > I would like to help you with that but I can't retrieve the repository:
> >
> > $ git clone git://git.kernel.org/pub/scm/qgit/qgit4.git qgit4.git
> > Initialized empty Git repository in d:/devel/git/qgit4/qgit4.git/.git/
> > git.kernel.org[0: 130.239.17.7]: errno=Invalid argument
> > git.kernel.org[1: 199.6.1.166]: errno=Bad file descriptor
> > git.kernel.org[2: 204.152.191.8]: errno=Bad file descriptor
> > git.kernel.org[3: 204.152.191.40]: errno=Bad file descriptor
> > fatal: unable to connect a socket (Bad file descriptor)
> > fetch-pack from 'git://git.kernel.org/pub/scm/qgit/qgit4.git' failed.
This looks familiar. It happens when there was no response to the 4 IPs
of git.kernel.org. This might be due to a firewall which blocks git://
> > $ git clone http://git.kernel.org/pub/scm/qgit/qgit4.git qgit4.git
> > Initialized empty Git repository in d:/devel/git/qgit4/qgit4.git/.git/
> > Cannot get remote repository information. Perhaps
> > git-update-server-info needs to be run there?
>
> Well, perhaps, but to clone with git protocol you don't need that.
It is generally a good idea to provide the server-info for dumb protocols,
because not everybody is fortunate enough (like you, evidently, because
you do not seem to care all that much...) to control her outbound firewall
restrictions.
Ciao,
Dscho
next prev parent reply other threads:[~2007-12-17 19:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 15:02 Windows binaries for qgit 2.0 Marco Costalba
2007-12-16 7:26 ` Abdelrazak Younes
2007-12-16 7:55 ` Marco Costalba
2007-12-16 8:52 ` Abdelrazak Younes
2007-12-16 9:05 ` Marco Costalba
2007-12-16 9:10 ` Abdelrazak Younes
2007-12-16 10:42 ` Marco Costalba
2007-12-16 11:11 ` Abdelrazak Younes
2007-12-16 22:26 ` Marco Costalba
[not found] ` <e5bfff550712161426y101c77efl4f5321d3440fed3f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-17 9:51 ` Abdelrazak Younes
2007-12-17 10:44 ` [msysGit] " Johannes Schindelin
2007-12-17 11:07 ` Abdelrazak Younes
2007-12-17 19:14 ` Marco Costalba
[not found] ` <e5bfff550712171114i40a59b11md87038a3fc13d29c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-17 21:40 ` Abdelrazak Younes
2007-12-17 19:05 ` Marco Costalba
2007-12-17 19:13 ` Johannes Schindelin [this message]
[not found] ` <Pine.LNX.4.64.0712171911070.9446-OGWIkrnhIhzN0uC3ymp8PA@public.gmane.org>
2007-12-17 19:17 ` Marco Costalba
2007-12-17 21:22 ` Abdelrazak Younes
[not found] ` <e5bfff550712171105k62b90853w1c5eed64bd11fb23-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-17 21:20 ` Abdelrazak Younes
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.0712171911070.9446@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mcostalba@gmail.com \
--cc=msysgit@googlegroups.com \
--cc=younes.a@free.fr \
/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).