All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Struberg <struberg@yahoo.de>
To: newsgroups@catchall.shelter13.net, Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Deciding between Git/Mercurial
Date: Sun, 27 Sep 2009 18:51:36 +0000 (GMT)	[thread overview]
Message-ID: <585748.13758.qm@web27802.mail.ukl.yahoo.com> (raw)
In-Reply-To: <81b0412b0909271144o26743e05uac3132cdc5b530b@mail.gmail.com>

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?

LieGrue,
strub

--- On Sun, 9/27/09, Alex Riesen <raa.lkml@gmail.com> wrote:

> From: Alex Riesen <raa.lkml@gmail.com>
> Subject: Re: Deciding between Git/Mercurial
> To: newsgroups@catchall.shelter13.net
> Cc: git@vger.kernel.org
> Date: Sunday, September 27, 2009, 8:44 PM
> On Sun, Sep 27, 2009 at 20:10, Anteru
> <newsgroups@catchall.shelter13.net>
> wrote:
> > Yeah, well, the main question here is actually: Is
> improved support for
> > Windows one of the goals of future git development, or
> is this a
> > complete non-issue?
> 
> I just hope it is not. Improved Windows support mostly
> means lots of dead code (and that's the best outcome),
> which no other platform can use.
> --
> To unsubscribe from this list: send the line "unsubscribe
> git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      

  reply	other threads:[~2009-09-27 18:51 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 [this message]
2009-09-27 19:18         ` Anteru
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=585748.13758.qm@web27802.mail.ukl.yahoo.com \
    --to=struberg@yahoo.de \
    --cc=git@vger.kernel.org \
    --cc=newsgroups@catchall.shelter13.net \
    --cc=raa.lkml@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.