From: Alex Riesen <raa.lkml@gmail.com>
To: newsgroups@catchall.shelter13.net
Cc: git@vger.kernel.org
Subject: Re: Deciding between Git/Mercurial
Date: Sun, 27 Sep 2009 21:31:50 +0200 [thread overview]
Message-ID: <81b0412b0909271231u54fbe035n3ce2503237b5ebf3@mail.gmail.com> (raw)
In-Reply-To: <h9odqq$ig9$1@ger.gmane.org>
On Sun, Sep 27, 2009 at 21:18, Anteru <newsgroups@catchall.shelter13.net> wrote:
> 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? ...
Despite what I said, this is very unlikely (sadly). There are active developers
whose professional life happens in Windows. Besides, the project is open-
source and no one can stop you from taking over the maintainership of a port.
> As I said, I'm happy with using msysgit, but I cannot find any roadmap
There isn't any. Roadmaps are for projects with a guaranteed end of life :-p
> 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"?
Not likely. OTOH, msysGIT does not have that part of performance problem.
next prev parent reply other threads:[~2009-09-27 19:36 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
2009-09-27 19:31 ` Alex Riesen [this message]
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=81b0412b0909271231u54fbe035n3ce2503237b5ebf3@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=newsgroups@catchall.shelter13.net \
/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.