From: Abdelrazak Younes <younes.a-GANU6spQydw@public.gmane.org>
To: msysgit-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Windows binaries for qgit 2.0
Date: Mon, 17 Dec 2007 10:51:52 +0100 [thread overview]
Message-ID: <fk5grp$7il$2@ger.gmane.org> (raw)
In-Reply-To: <e5bfff550712161426y101c77efl4f5321d3440fed3f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Marco Costalba wrote:
> On Dec 16, 2007 12:11 PM, Abdelrazak Younes <younes.a-GANU6spQydw@public.gmane.org> wrote:
>> Actually you might prefer to just use the LyX dependencies package that
>> we provide for Windows developers, it contains Qt. I paste here the
>> relevant part of our 'INSTALL.Win32':
>>
>
> Thanks, I've tried it but without success because I need MSVC 2005
> installed, and currently is not.
Right.
>
> Anyhow for now I have produced a version with mingw that seems more or
> less to work, when I have a bit of time I will install MSVC 2005 and
> try if with that compiler is better...
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.
$ 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?
$ git --version
git version 1.5.3.6.1791.gfd264
'git clone ssh://...' seems to work but I guess I need a login and password?
Maybe I am doing something wrong here? Sorry, my first time ever with git...
Abdel.
PS: Sorry for the cross posting but I guess this issue is maybe of
interest to msysgit people.
next prev parent reply other threads:[~2007-12-17 9:55 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 [this message]
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
[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='fk5grp$7il$2@ger.gmane.org' \
--to=younes.a-ganu6spqydw@public.gmane.org \
--cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=msysgit-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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).