public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@jifvik.org>
To: Alex Schuilenburg <alexs@ecoscentric.com>
Cc: eCos discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS]  eCos VCS switch
Date: Thu, 17 Sep 2009 21:15:00 -0000	[thread overview]
Message-ID: <4AB2A6DA.4080005@jifvik.org> (raw)
In-Reply-To: <4AB24B97.4040204@ecoscentric.com>

Alex Schuilenburg wrote:
> 
>>A switch of the public CVS repository to Mercurial would be a major
>>improvement.
>>  
> 
> Agreed.  My initial findings are also that mercurial is the preferred
> solution.  It is not as powerful as git, or even as fast,

By "more powerful", do you mean git allows you to do anything of 
significance that hg/bzr doesn't? I didn't think there was from my own 
checking, but I'm prepared to be corrected.

Or by any chance do you mean that it's more powerful/fast if you have the 
ability to remember which of the gazillion different git commands to use 
with precisely which set of arcane options. Then it's a speedy one-liner!

Personally I would need a lot of convincing to use git. Or more precisely, 
to make the eCos community with its breadth of users with varying 
experience do so. I think it would raise the bar to using eCos in a very 
negative way.

The only thing that might ameliorate it would be something like 
http://code.google.com/p/tortoisegit/ but it seems like early days for 
that, I'm not impressed by their webpage, it seems to have restricted 
capabilities (but I may well be wrong on this count), and at best it's 
playing catch-up with the others.

Jifl
-- 
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2009-09-17 21:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 14:45 Alex Schuilenburg
2009-09-17 21:15 ` Jonathan Larmour [this message]
2009-09-17 22:56   ` Alex Schuilenburg
2009-09-18 10:08   ` [ECOS] " Sergei Organov
2009-09-18 10:41   ` Sergei Organov
2009-09-18 12:05     ` Alex Schuilenburg
2009-09-18 12:20       ` Daniel Néri

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=4AB2A6DA.4080005@jifvik.org \
    --to=jifl@jifvik.org \
    --cc=alexs@ecoscentric.com \
    --cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).