From: Alex Schuilenburg <alexs@ecoscentric.com>
To: ecos-maintainers@ecos.sourceware.org
Subject: Mercurial or GIT conversion
Date: Mon, 14 Dec 2009 11:13:00 -0000 [thread overview]
Message-ID: <4B261DD2.3010907@ecoscentric.com> (raw)
Dear Maintainers
It has been quite a while since a number of us had the DRCS discussion
on ecos-discuss regarding the switch of RCS used for eCos from CVS to
<insert-favourite-DRCS-here>. Not much appears to have happened since.
I would like to remind you that this request for conversion was largely
spurred by the community as well as eCosCentric, who have also provided
a mercurial version of the eCos repository which could either be adopted
or used as the basis of a git conversion by you (the maintainers) on
sourceware (depending on which of the two favourite DRCS systems is
selected).
Has this been forgotten? I would not like to see this fallen by the
wayside and I know from IRL discussions with the maintainers at
eCosCentric that at least some of the maintainers are eager to see a
conversion to a DRCS.
Can you please provide me, or even better, the community, with a status
update on where we all are at with regard to this?
Thanks
-- Alex Schuilenburg
Managing Director/CEO eCosCentric Limited
www.ecoscentric.com Reg in England and Wales, Reg No 4422071
reply other threads:[~2009-12-14 11:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B261DD2.3010907@ecoscentric.com \
--to=alexs@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.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).