From: Sergei Organov <osv@javad.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: eCos VCS switch
Date: Fri, 18 Sep 2009 10:08:00 -0000 [thread overview]
Message-ID: <h8vm4g$mhu$1@ger.gmane.org> (raw)
In-Reply-To: <4AB2A6DA.4080005@jifvik.org>
Jonathan Larmour <jifl@jifvik.org> writes:
[...]
> 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.
Then just go with mercurial or bazaar for now, as all they are still so
much better than CVS anyway.
And then, in 2--3 years, after a taste in DVCS evolves, it will be much
easier to finally switch to git ;-)
-- 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
next prev parent reply other threads:[~2009-09-18 10:08 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 ` Sergei Organov [this message]
2009-09-18 10:41 ` [ECOS] " 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='h8vm4g$mhu$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).