From: Grant Edwards <grante@visi.com>
To: Jonathan Larmour <jlarmour@redhat.co.uk>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] eCos Networking support
Date: Wed, 28 Jun 2000 13:33:00 -0000 [thread overview]
Message-ID: <20000628203336.A5071@visi.com> (raw)
In-Reply-To: <395A60B0.EBF36CF8@redhat.co.uk>
On Wed, Jun 28, 2000 at 09:31:44PM +0100, Jonathan Larmour wrote:
> But the choice of what constitutes an "important" change
> depends most of all on the application using the code, so it's
> unlikely we'd find the right balance for everyone. It can only
> be up to you to determine the significance of the changes, and
> the consequent risk to your app involved; which is why the
> ChangeLogs are there. For anything more than that... well
> that's why we sell support :-).
I suppose it's hard to make a living if you give _everything_
away for free. :)
--
Grant Edwards
grante@visi.com
prev parent reply other threads:[~2000-06-28 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-28 1:13 Amit Agrawal
2000-06-28 8:04 ` Jonathan Larmour
2000-06-28 8:09 ` Andrew Lunn
2000-06-28 12:03 ` Grant Edwards
2000-06-28 13:31 ` Jonathan Larmour
2000-06-28 13:33 ` Grant Edwards [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=20000628203336.A5071@visi.com \
--to=grante@visi.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@redhat.co.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).