public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Organov <osv@javad.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  Re: eCos VCS switch
Date: Fri, 18 Sep 2009 10:41:00 -0000	[thread overview]
Message-ID: <h8vo3c$sg6$1@ger.gmane.org> (raw)
In-Reply-To: <4AB2A6DA.4080005@jifvik.org>

Jonathan Larmour <jifl@jifvik.org> writes:

> 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.

git rebase

is my favorite and is very handy to maintain changes w.r.t official
repository to be then contributed back. BTW, rebasing is what CVS
actually does with your local changes when you do 'cvs update'. Except
git rebase is much more safe and convenient. I can't tell if hg or bzr
already have something similar though as they seem to borrow features
from each other rather quickly.

My personal order of preference is: git, hg, bzr. But once again, the
differences between those 3 are minor compared to advantages any of them
has compared to CVS ;-)

-- Sergei.


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

  parent reply	other threads:[~2009-09-18 10:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 14:45 [ECOS] " Alex Schuilenburg
2009-09-17 21:15 ` Jonathan Larmour
2009-09-17 22:56   ` Alex Schuilenburg
2009-09-18 10:08   ` [ECOS] " Sergei Organov
2009-09-18 10:41   ` Sergei Organov [this message]
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='h8vo3c$sg6$1@ger.gmane.org' \
    --to=osv@javad.com \
    --cc=ecos-discuss@sources.redhat.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 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).