From: Jonathan Larmour <jlarmour@redhat.com>
To: Sergio Nunes <snunes@Celestica.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] ConfigTool2.0
Date: Fri, 08 Jun 2001 11:11:00 -0000 [thread overview]
Message-ID: <3B21155A.A5794102@redhat.com> (raw)
In-Reply-To: <85256A65.0062C58B.00@TORMTA1.ca-tor.celestica.com>
Sergio Nunes wrote:
>
> I assume you can't use 1.3.1.2 Configtool with eCos 1.3.1. At least when I tried
> I got the following:
[snip]
Yep. There's a note on http://sources.redhat.com/ecos/anoncvs.html saying
that.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/
next prev parent reply other threads:[~2001-06-08 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-08 11:00 Sergio Nunes
2001-06-08 11:11 ` Jonathan Larmour [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-08 11:58 Sergio Nunes
2001-06-08 8:15 Trenton D. Adams
2001-06-08 10:19 ` Jonathan Larmour
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=3B21155A.A5794102@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=snunes@Celestica.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).