From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: MinGW port (was: Re: [ANNOUNCE] qgit4 aka qgit ported to Windows)
Date: Thu, 11 Jan 2007 10:35:41 +0100 [thread overview]
Message-ID: <45A604ED.5EF73A1E@eudaptics.com> (raw)
In-Reply-To: 46a038f90701101517s1d5e818eq2fba220d17a6aa03@mail.gmail.com
Martin Langhoff wrote:
> 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?
FWIW, I'm slowly working on a MinGW port of git, based on Dscho's
initial work.
Currently, the tool set passes about 60-70% of the tests.
This works: The tools that you commonly need to work on a local repo,
except merges ([*]): commit, rebase, reset, log, diff and their
plumbing.
This does not work: pull, fetch, clone; mostly due to fork()
difficulties in their plumbing (fetch-pack, send-pack, etc.)
[*] because shell scripts like merge-one-file can't be invoked from an
exe like merge-index, yet. Fortunately this looks like the easiest part
to solve.
-- Hannes
next prev parent reply other threads:[~2007-01-11 9:35 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 ` Johannes Sixt [this message]
2007-01-11 9:39 ` MinGW port (was: Re: [ANNOUNCE] qgit4 aka qgit ported to Windows) 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
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=45A604ED.5EF73A1E@eudaptics.com \
--to=j.sixt@eudaptics.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).