From: Andreas Ericsson <ae@op5.se>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Martin Langhoff <martin.langhoff@gmail.com>,
GIT list <git@vger.kernel.org>, Petr Baudis <pasky@suse.cz>
Subject: Re: [ANNOUNCE] qgit4 aka qgit ported to Windows
Date: Thu, 11 Jan 2007 13:27:44 +0100 [thread overview]
Message-ID: <45A62D40.5040707@op5.se> (raw)
In-Reply-To: <e5bfff550701110419v3508e9d5gbc206b7d0fa320ae@mail.gmail.com>
Marco Costalba wrote:
> On 1/11/07, Martin Langhoff <martin.langhoff@gmail.com> wrote:
>> On 1/10/07, Marco Costalba <mcostalba@gmail.com> wrote:
>> > 6) Start qgit.exe
>> > 7) Have fun
>>
>> Great!
>>
>> How much does qgit4 depend on using commandline git? IOWs, how far
>> from not needing cygwin+git, and shipping a git+qgit compiled against
>> the MinGW that QT4 has?
>>
>
> qgit4 does not depends on commandline git environment at all. You can
> start qgit4 also without a git installation, also without a cygwin
> installation either. Of course it's not useful in that cases.
>
Huh? Does qgit4 have all the git plumbing built in?
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-01-11 12:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 21:14 [ANNOUNCE] qgit4 aka qgit ported to Windows Marco Costalba
2007-01-09 21:55 ` Josef Weidendorfer
2007-01-09 22:30 ` Marco Costalba
2007-01-09 22:47 ` Yann Dirson
2007-01-10 23:17 ` Martin Langhoff
2007-01-11 8:47 ` Johannes Schindelin
2007-01-11 9:35 ` MinGW port (was: Re: [ANNOUNCE] qgit4 aka qgit ported to Windows) Johannes Sixt
2007-01-11 9:39 ` Johannes Schindelin
2007-01-11 12:56 ` Marco Costalba
2007-01-11 13:24 ` Johannes Sixt
2007-01-11 12:19 ` [ANNOUNCE] qgit4 aka qgit ported to Windows Marco Costalba
2007-01-11 12:27 ` Andreas Ericsson [this message]
2007-01-11 12:49 ` Marco Costalba
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=45A62D40.5040707@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
--cc=mcostalba@gmail.com \
--cc=pasky@suse.cz \
/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).