From: Andy Whitcroft <apw@shadowen.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Mozilla, git and Windows
Date: Mon, 27 Nov 2006 15:34:22 +0000 [thread overview]
Message-ID: <456B057E.4000904@shadowen.org> (raw)
In-Reply-To: <9e4733910611270728p36e58e08w6cc7a2989b7843ce@mail.gmail.com>
Jon Smirl wrote:
> In the other thread we are discussing the conversion of Mozilla CVS to
> git format. This is something that has to be done but it is not the
> only issue. Without a native Windows port they won't even consider
> using git. There is also the risk that the features needed by Mozilla
> will be completed after they choose to use a different SCM.
>
> Even if we implement all of the needed features git still needs to win
> the competition against the other possible choices. The last I heard
> the leading candiate is SVN/SVK.
Do we need to worry too much about taking over the world in one day?
Yes of course git is _the_ superior solution etc, but too many new users
at once is always painful.
I think you are more likely to win letting them convert over to SVN.
From there people naturally start using git mirrors from the SVN trunk.
Cirtainly I have two projects which do not use git, one in CVS and one
in SVN. I just svnimport that and work in git. I am confident with
time the project will migrate, but I am happy other git users are happy
all without it being the tool of choice.
-apw
next prev parent reply other threads:[~2006-11-27 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 15:28 Mozilla, git and Windows Jon Smirl
2006-11-27 15:34 ` Andy Whitcroft [this message]
2006-11-27 16:13 ` Jon Smirl
2006-11-27 16:37 ` Robin Rosenberg
2006-11-27 22:13 ` Petr Baudis
2006-11-28 1:35 ` Jon Smirl
2006-11-28 12:17 ` Michael Haggerty
2006-11-28 0:30 ` Sam Vilain
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=456B057E.4000904@shadowen.org \
--to=apw@shadowen.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.