From: Gary Thomas <gary@mlbassoc.com>
To: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Deprecating eCos 2.0
Date: Wed, 12 Jul 2006 14:03:00 -0000 [thread overview]
Message-ID: <44B50114.6070004@mlbassoc.com> (raw)
Can we make the automated download tool (ecos-install.tcl) use
a CVS snapshot instead of the old 2.0? It would solve so many
"I'm using 2.0 ..." issues if this was the default.
Note: I don't care if it still downloads the old tools (which
are also labeled 2.0) as for the most part, they don't get
in the way.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2006-07-12 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 14:03 Gary Thomas [this message]
2006-07-12 15:03 ` Jonathan Larmour
2006-07-22 17:40 ` Andrew Lunn
2006-07-22 22:52 ` Jonathan Larmour
2006-07-24 17:58 ` John Dallaway
2006-07-31 8:43 ` Andrew Lunn
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=44B50114.6070004@mlbassoc.com \
--to=gary@mlbassoc.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).