From: Andrew Lunn <andrew@lunn.ch>
To: "Doyle, Patrick" <WPD@dtccom.com>
Cc: "'ecos-devel@sources.redhat.com'" <ecos-devel@sources.redhat.com>
Subject: Re: flash_v2 status
Date: Wed, 08 Mar 2006 08:46:00 -0000 [thread overview]
Message-ID: <20060308084632.GA32333@lunn.ch> (raw)
In-Reply-To: <3EDBCCE80E95E744A99895CA464987C4A7D28A@dtcsrvr09>
On Tue, Mar 07, 2006 at 04:52:04PM -0500, Doyle, Patrick wrote:
> Greetings fellow travellers,
>
> Could somebody tell me what the current status of flash_v2 is? Did I miss
> an announcement that it had been merged into the main tree? (entirely
> possible) I found a message from Jani asking the same thing last June. Any
> thoughts?
Such a merge is potentially disruptive. So it was planned to happen at
the next major release of eCos. This will happen then all the FSF
issues are resolved......
Andrew
prev parent reply other threads:[~2006-03-08 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 21:44 Doyle, Patrick
2006-03-08 8:46 ` Andrew Lunn [this message]
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=20060308084632.GA32333@lunn.ch \
--to=andrew@lunn.ch \
--cc=WPD@dtccom.com \
--cc=ecos-devel@sources.redhat.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).