public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@imag•fr>
To: git@vger•kernel.org
Subject: Re: Google Summer of Code 2007
Date: Wed, 28 Feb 2007 10:03:31 +0100	[thread overview]
Message-ID: <vpq4pp6r6vw.fsf@olympe.imag.fr> (raw)
In-Reply-To: <200702280842.08279.andyparkins@gmail.com> (Andy Parkins's message of "Wed\, 28 Feb 2007 08\:42\:07 +0000")

Andy Parkins <andyparkins@gmail•com> writes:

> 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.

+ 1. It seems the windows port somewhat has the status "we want it but
I'm not going to do it" for most git contributors.

I'm personnally using unix 99% of the time, but I also have a piece of
windows installed on my laptop. For example, I'm working on a small
project using windows-only software, and being able to use git
comfortably from this setup would be cool.

Also, I'm relucant to migrate to git completely even for unix-only
projects, since I know that a hypothetical future windows-port will be
made hard by the non-availability of the windows port.

> Given that the best thing for git in the long term is more users, 

That's what I feel. The problem with distributed SCMs at the moment is
that there are too many of them, not sharing enough users. For
example, I had to choose a replacement for CVS with some colleagues
recently. I argued about using a distributed one, but the argument
against, and the decision was "SVN is what they're more likely to use
later, let's go for SVN no matter how bad it is".

> 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.

Sure. One of the best examples being Mozilla. I hardly see them using
a piece of software that's not working properly on windows, since the
majority of users (and probably of the developers, I don't know) are
running windows.

-- 
Matthieu

  reply	other threads:[~2007-02-28  9:03 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
2007-02-28  9:03   ` Matthieu Moy [this message]
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=vpq4pp6r6vw.fsf@olympe.imag.fr \
    --to=matthieu.moy@imag$(echo .)fr \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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