From: Johannes Sixt <j.sixt@viscovery.net>
To: dhruva <dhruva@ymail.com>
Cc: Kevin Yu <yujie052@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Windows: git-shell can be compiled again
Date: Mon, 08 Sep 2008 13:53:40 +0200 [thread overview]
Message-ID: <48C51244.6060807@viscovery.net> (raw)
In-Reply-To: <321897.23044.qm@web95004.mail.in2.yahoo.com>
dhruva schrieb:
> Are there any M$ specific issues still out there that needs some attention? I could help on stuff that does not require git internal knowledge. Are there some M$ specific performance issues that I could try to help? Let me know, I will try my best to help. I need to have git on both GNU/linux and M$ platforms for day job.
In order of increasing difficulty:
- Run the tests on different platforms and servicepack levels.
- Get proficient in building the installer for a release.
- Find a way to build perl scripts that is acceptable for upstream git.git
and that also works on MSYS/MinGW. Currently we still modify the build
procedure, and the results do not work during 'make test'.
- Give some love to git-svn.perl. It will be removed from msysgit's
1.6.0.x release because it raises expectations that cannot be fulfilled.
Please dig the list archive: http://groups.google.com/group/msysgit
I don't think a lot can be done performance-wise unless you want to help
port scripts to C.
-- Hannes
next prev parent reply other threads:[~2008-09-08 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 11:31 [PATCH] Windows: git-shell can be compiled again dhruva
2008-09-08 11:53 ` Johannes Sixt [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-08 12:12 dhruva
2008-09-08 12:22 ` Johannes Sixt
2008-09-08 8:22 What's the status of MinGW port dhruva
2008-09-08 10:46 ` [PATCH] Windows: git-shell can be compiled again Johannes Sixt
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=48C51244.6060807@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=dhruva@ymail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=yujie052@gmail.com \
/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).