From: Anteru <newsgroups@catchall.shelter13.net>
To: git@vger.kernel.org
Subject: Re: Deciding between Git/Mercurial
Date: Sun, 27 Sep 2009 21:18:49 +0200 [thread overview]
Message-ID: <h9odqq$ig9$1@ger.gmane.org> (raw)
In-Reply-To: <585748.13758.qm@web27802.mail.ukl.yahoo.com>
Mark Struberg schrieb:
> Another thing to consider: For what kind of project/language do you need git? What build tools are you using and how good is the integration into both git and hg?
The project is running on Windows/Linux (Windows being the primary
development platform, and we also expect most users to run Windows.)
For tooling, we use Trac at the moment (good integration with SVN), but
we're evaluating GitTrac, Trac/Mercurial and Redmine now (+ possible
migration paths.) For our build system, it's a non-issue anyway, as
git/mercurial have command line clients, and that's all we need.
Don't get me wrong with Git+msysgit on Windows, the point is simply if
we switch to git, can we expect that Windows will be supported for the
foreseeable future or is it possible that git may simply drop Windows
support completely? For Mercurial, this is a non-issue, as it is written
in Python, and Python will support both Windows and Linux.
As I said, I'm happy with using msysgit, but I cannot find any roadmap
etc. which helps me to determine how git and Windows is going to
continue (for instance, I can find some complaints that git's
performance is bad on Windows due to cygwin's fork()/exec(), is this
likely to get ever "fixed"? I guess git# will solve this as soon as it's
ready?)
Cheers,
Anteru
next prev parent reply other threads:[~2009-09-27 19:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 12:24 Deciding between Git/Mercurial Anteru
2009-09-27 18:01 ` Robin Rosenberg
2009-09-27 18:10 ` Anteru
2009-09-27 18:44 ` Alex Riesen
2009-09-27 18:51 ` Mark Struberg
2009-09-27 19:18 ` Anteru [this message]
2009-09-27 19:31 ` Alex Riesen
2009-09-27 19:34 ` Erik Faye-Lund
2009-09-27 18:55 ` Pascal Obry
2009-10-22 8:01 ` Martin Langhoff
2009-09-28 8:36 ` Felipe Contreras
2009-09-28 8:42 ` Matthieu Moy
2009-09-28 10:08 ` Johannes Schindelin
2009-09-28 11:01 ` Felipe Contreras
2009-09-28 11:17 ` Bruce Stephens
2009-09-30 11:14 ` Matthias Andree
2009-09-28 11:32 ` Dilip M
2009-09-28 20:54 ` Damien Wyart
2009-09-28 21:09 ` Steven Noonan
2009-09-28 21:33 ` Sverre Rabbelier
2009-09-28 23:56 ` Randal L. Schwartz
2009-09-29 0:01 ` Sverre Rabbelier
2009-09-29 7:44 ` Mike Ralphson
2009-09-29 8:21 ` Matthieu Moy
2009-09-29 8:22 ` Sverre Rabbelier
2009-09-28 23:11 ` Jakub Narebski
2009-09-29 0:32 ` Jakub Narebski
2009-09-29 6:32 ` Anteru
2009-09-29 18:44 ` Leo Razoumov
2009-09-29 18:58 ` Jakub Narebski
2009-09-29 19:55 ` Matthieu Moy
2009-09-30 0:49 ` Leo Razoumov
2009-09-30 6:28 ` Björn Steinbrink
2009-09-30 9:17 ` Andreas Ericsson
2009-09-30 11:09 ` Jakub Narebski
2009-09-29 1:55 ` Paolo Bonzini
2009-09-29 8:44 ` Daniele Segato
2009-09-29 8:54 ` Dilip M
2009-09-30 11:09 ` Matthias Andree
2009-09-30 22:05 ` Daniel Barkalow
2009-10-22 2:38 ` Dilip M
2009-10-22 6:50 ` Anteru
2009-10-22 7:12 ` Dilip M
2009-10-22 7:35 ` Anteru
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='h9odqq$ig9$1@ger.gmane.org' \
--to=newsgroups@catchall.shelter13.net \
--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).