From: Jonathan Larmour <email@example.com>
To: Sergei Gavrikov <firstname.lastname@example.org>
Cc: John Dallaway <email@example.com>,
eCos Maintainers <firstname.lastname@example.org>,
Evgeniy Dushistov <email@example.com>,
Daniel Helgason <firstname.lastname@example.org>
Subject: Re: Getting Atmel AT91SAM9 into eCos
Date: Tue, 09 Mar 2010 16:30:00 -0000 [thread overview]
Message-ID: <4B967798.email@example.com> (raw)
[ snip good stuff from Sergei ]
On 09/03/10 02:00, Sergei Gavrikov wrote:
> I'm sorry, I have no answer on the John's "far-reaching" question the
> below, but, IMO "ARM9 v2" branch under CVS control can take the same
> long period as "FLASH v2" took the time under CVS before that was merged
> with mainstream.
One of the main difficulties there was directly because of CVS. The
trunk had moved on (particularly in RedBoot's flash support), so there
was a lot of overhead to merging.
These merge headaches would be much less with a modern VCS, so it won't
be as scary to merge. Which is a big reason why people kept putting it off.
> Let's get even first experimental trunk of eCos under
> DVCS. It is important that with distributed VCS of eCos we would
> collaborate with contributors more effectively. Well, this is my
> look/feel only.
Clearly you're keen on distributed :-). I agree, but we'll discuss
elsewhere. I'll try and get a mail out today.
next prev parent reply other threads:[~2010-03-09 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
2010-02-23 9:26 ` John Dallaway
2010-02-23 9:58 ` Evgeniy Dushistov
2010-02-23 16:53 ` Gary Thomas
2010-02-23 17:50 ` Evgeniy Dushistov
2010-03-08 13:11 ` John Dallaway
2010-03-08 13:54 ` Jonathan Larmour
2010-03-08 15:59 ` John Dallaway
2010-03-09 2:00 ` Sergei Gavrikov
2010-03-09 16:30 ` Jonathan Larmour [this message]
2010-03-09 16:25 ` Jonathan Larmour
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).