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

Jonathan Larmour wrote:
> 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!
Neither. Some complex jobs may take a couple of commands in hg, but a
single command may exist in git to do that job.  That kind of "more
powerful".  Certainly there is nothing I have seen that you cannot do in
hg that you can in git.

As for the gazillion commands, I agree with your sentiments. However, I
have seen git users defend this by saying that the same exists of hg,
only you type hg before the command.  hg extensions are a simple example
:-)  However, hg help is a lot easier than "now what command was it to
..." 

>
> 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.
I agree.  The learning curve of git is very steep which IMHO will just
get in the way of development and ease of use for the average user.  hg
have a simple set which is close to CVS anyway, so there is an ease and
familiarity of use for CVS users using hg.  I also strongly recommend
the hg book "Mercurial: The Definitive Guide" since it has a well
written explanation that helps those entrenched with CVS and SVN models
to get their head around the distributed RCS model.  Available online at
http://hgbook.red-bean.com/ and most decent bookstores.  I have found no
equivalent for git or bazaar.

We could always wait for something better to come along - this is
software, so something normally does - but then we would wait forever
and stay with an 80's RCS while the rest of the world progress.

-- Alex Schuilenburg

   >>>> Visit us at ESC-Boston  http://www.embedded.com/esc/boston <<<<
   >>>> Sep 22-23 on Stand 226  at Hynes Convention Center, Boston <<<<

          **** Visit us at ESC-UK  http://www.embedded.co.uk ****
          **** Oct 7-8 on Stand 433 at FIVE ISC, Farnborough ****


-- 
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 22:56 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
2009-09-17 22:56   ` Alex Schuilenburg [this message]
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=4AB2BEA4.4050409@ecoscentric.com \
    --to=alexs@ecoscentric.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=jifl@jifvik.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).