From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: Google Summer of Code 2007
Date: Wed, 28 Feb 2007 08:42:07 +0000 [thread overview]
Message-ID: <200702280842.08279.andyparkins@gmail.com> (raw)
In-Reply-To: <20070225075917.GC1676@spearce.org>
On Sunday 2007 February 25 07:59, Shawn O. Pearce wrote:
> Thoughts?
What about the oft-asked for windows port? From what I've seen, none of the
Unix types have any incentive to do this, so a financial incentive might be
just the thing.
Perhaps the windows port is already far enough along that this wouldn't be a
big job. In which case the project could be windows shell integration (or
whatever other candy-based device a windows user would need to easily use
git).
Project title: "Make it so that one .exe click-and-install would make the full
power of git available in an idiot^H^H^H^H^H typical-GUI-using-developer
friendly form"
Given that the best thing for git in the long term is more users, and that no
windows support is the commonly given reason why other SCMs are chosen
instead, this would be a good use of the resources.
I'm off to shower, I feel dirty even talking about Windows :-)
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-02-28 8:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 7:59 Google Summer of Code 2007 Shawn O. Pearce
2007-02-27 20:47 ` Johannes Schindelin
2007-02-28 8:42 ` Andy Parkins [this message]
2007-02-28 9:03 ` Matthieu Moy
2007-03-02 20:36 ` Johannes Schindelin
2007-02-28 9:35 ` Raimund Bauer
2007-02-28 15:39 ` Brian Gernhardt
2007-02-28 15:47 ` Shawn O. Pearce
2007-02-28 16:00 ` Brian Gernhardt
2007-03-01 2:08 ` Jakub Narebski
2007-03-01 8:03 ` Matthieu Moy
2007-03-01 21:34 ` Shawn O. Pearce
2007-03-04 22:10 ` Martin Langhoff
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=200702280842.08279.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).