From: Julian Smart <julians@redhat.com>
To: "Trenton D. Adams" <tadams@extremeeng.com>
Cc: eCos <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] NASTY bug in eCos ConfigTool 1.3.1.2 Win32
Date: Wed, 13 Jun 2001 06:06:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20010613140835.00c414e0@pop> (raw)
In-Reply-To: <XFMail.20010613061340.gthomas@cambridge.redhat.com>
At 06:13 AM 6/13/01 -0600, Gary Thomas wrote:
>On 12-Jun-2001 Trenton D. Adams wrote:
> > I have two separate configs. The are identical except one is RAM, and
> > the other is ROM support for the kernel. If I change from ROM to RAM
> > support, it doesn't allow me to save the new configuration under the
> > current project. I have to select File|Exit in order for it to ask me
> > to save and then it will finally acutally save it. This caused me to
Do you think you could list the steps involved? I'm not sure I understand
what you mean by not allowing you to save it.
Thanks,
Julian
--
Red Hat UK Ltd, Unit 200 Rustat House, 62 Clifton Road, Cambridge, UK. CB1
7EG Tel: +44 (1223) 271063
next prev parent reply other threads:[~2001-06-13 6:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 15:02 Trenton D. Adams
2001-06-13 5:14 ` Gary Thomas
2001-06-13 6:06 ` Julian Smart [this message]
2001-06-13 7:44 ` Trenton D. Adams
2001-06-13 11:08 ` Jonathan Larmour
2001-06-13 11:15 ` Trenton D. Adams
2001-06-13 7:42 ` Trenton D. Adams
2001-06-13 7:54 ` Gary Thomas
2001-06-13 7:59 ` Trenton D. Adams
2001-06-13 11:05 ` Jonathan Larmour
[not found] <4.2.0.58.20010613154832.00c13bc0@pop>
2001-06-13 8:15 ` Trenton D. Adams
2001-06-14 8:20 ` Julian Smart
2001-06-13 10:40 Dan Conti
2001-06-13 12:19 ` Jonathan Larmour
2001-06-13 13:47 ` Lewin A.R.W. Edwards
2001-06-14 3:42 ` Gary Thomas
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=4.2.0.58.20010613140835.00c414e0@pop \
--to=julians@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=tadams@extremeeng.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).