From: Andrew Lunn <andrew.lunn@ascom.ch>
To: John Dallaway <john@dallaway.org.uk>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Deprecating eCos 2.0
Date: Mon, 31 Jul 2006 08:43:00 -0000 [thread overview]
Message-ID: <20060731084339.GC30932@donkey.ma.tech.ascom.ch> (raw)
In-Reply-To: <44C50A4C.6090400@dallaway.org.uk>
My access to email has been a bit spotty, so sorry about taking so
long to reply. Im back home now, but life is still a bit chaotic.
It seems like we are staying with a version number. O.K.
Then i suggest we modify the Download and Install page. Add some text
about what the release snapshot is and is not and what the anonycvs is
and is not. Also, make sure the date for the release snapshot is
clearly stated.
This would make it clearer when somebody is doing there first download
as to what they are getting and should hopefully reduce some of our
problems with historical code.
Andrew
prev parent reply other threads:[~2006-07-31 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 14:03 Gary Thomas
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 [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=20060731084339.GC30932@donkey.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).