From: "rrichardson7" <rrichardson7@cox.net>
To: <ecos-maintainers@ecos.sourceware.org>
Subject: Submission Standards/Guidance
Date: Mon, 05 Sep 2005 03:53:00 -0000 [thread overview]
Message-ID: <00cd01c5b1cd$3c8c8020$6ccae144@EngAtPlayWS> (raw)
While working with Hypercom, I'd had the pleasure of helping to implement
eCos onto power-Pc platform.
Notable mods we'd made, but not published, were to the memory caching macros
(have an explanation for why the flush macros "did not seem to work", and a
variation of the dlmalloc that allowed us to track instances of dynamic
memory loss/corruption). Those solutions were internally focused - ie. not
made for general consumption, which is why I gather that they were not
published.
Since that company has recently decided to "go in a different direction",
I'm no longer restricted from making such changes suitable for general
consumption. What are the guide lines for doing so?
next reply other threads:[~2005-09-05 3:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 3:53 rrichardson7 [this message]
2005-09-05 10:01 ` John Dallaway
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='00cd01c5b1cd$3c8c8020$6ccae144@EngAtPlayWS' \
--to=rrichardson7@cox.net \
--cc=ecos-maintainers@ecos.sourceware.org \
/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).