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

Sergei Organov wrote on 2009-09-18 11:40:
> 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.
>   

hg rebase [--source rev | --base rev] [--dest rev] | [--collapse] | [--continue] | [--abort] | [--keep]


The rebase extension is distributed as part of the standard mercurial
release :-)

As I said, I have not found any additional functionality provided by git
that you cannot do in mercurial ;-)

My favourite hg extension is forest which allows you to create a single
repository consisting of several other repositories, kind of like CVS
modules. In other words, you can work with all the repositories, or just
with subsets.  This means that multiple changes can be push/pulled
into/from multiple repositories, using a single standard hg push/pull
commands, as well as all the usual hg commands and functionality.  I
have not heard of equivalent functionality in git ;-)

-- 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-18 12:05 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
2009-09-18 12:05     ` Alex Schuilenburg [this message]
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=4AB37791.7090601@ecoscentric.com \
    --to=alexs@ecoscentric.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=osv@javad.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).