public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: John Dallaway <jld@ecoscentric.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Patches for the eCos 2.0 branch
Date: Tue, 18 Mar 2003 13:48:00 -0000	[thread overview]
Message-ID: <1047995318.7459.2925.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <200303180848.24682.jld@ecoscentric.com>

On Tue, 2003-03-18 at 01:48, John Dallaway wrote:
> [ moving from ecos-patches to ecos-maintainers ]
> 
> Gary, Nick and all
> 
> Nick Garnett wrote:
> 
> > Gary Thomas <gary@mlbassoc.com> writes:
> 
> >> You know me - I'm always interested in more [debug] information :-)
> >> By all means, apply this, and the QUICC changes as well.
> 
> > Currently I have applied this only to the trunk, since the v2.0 branch
> > does not have the changes that you made to the CPM/DPRAM allocator.
> > Were you going to apply these to the v2 branch, was there some reason
> > not to do that? If you are awaiting approval consider it given.
> 
> To avoid invalidating beta testing, we need to be very careful about what 
> goes into the 2.0 branch. Does the CPM/DPRAM allocator patch address a 
> known problem or is it purely delivering a new feature?
> 

IMO it addresses a long-standing deficiency. 

> I would like to see some more formal consensus among the maintainers on what 
> goes in to the 2.0 branch from here on.

Just doing as I was asked.
-- 
------------------------------------------------------------
Gary Thomas                 |
MLB Associates              |  Consulting for the
+1 (970) 229-1963           |    Embedded world
http://www.mlbassoc.com/    |
email: <gary@mlbassoc.com>  |
gpg: http://www.chez-thomas.org/gary/gpg_key.asc
------------------------------------------------------------

  reply	other threads:[~2003-03-18 13:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18  8:47 John Dallaway
2003-03-18 13:48 ` Gary Thomas [this message]
2003-03-18 16:04   ` Proposal for processing patches " John Dallaway
2003-03-18 17:25     ` Jonathan Larmour
2003-03-18 18:21       ` Nick Garnett
2003-03-18 18:56     ` Andrew Lunn
2003-04-12  5:00       ` Jonathan Larmour
2003-04-14  7:28         ` Andrew Lunn
2003-03-18 19:01     ` Andrew Lunn
2003-03-18 22:58       ` Jonathan Larmour
2003-03-18 19:16     ` SNMP for FreeBSD Andrew Lunn
2003-03-19 13:22       ` Jonathan Larmour
2003-03-19 14:23         ` Gary Thomas
2003-03-19 18:07         ` Nick Garnett
2003-03-25 17:01       ` Andrew Lunn
2003-03-19 14:22     ` 2.0 branch: mn10300 debug info patch Bart Veer
2003-03-19 14:40       ` John Dallaway
2003-03-19 18:07       ` Nick Garnett
2003-03-18 18:09   ` Patches for the eCos 2.0 branch Nick Garnett
2003-03-18 18:25     ` Gary Thomas
2003-03-18 19:05       ` Nick Garnett
2003-03-18 19:13         ` Gary Thomas
2003-03-19 10:18           ` New CPM/DPRAM allocator John Dallaway
2003-03-19 13:02             ` Nick Garnett
2003-03-19 14:38               ` Gary Thomas
2003-03-19 15:44               ` John Dallaway
2003-03-19 17:06                 ` Gary Thomas
2003-03-19 18:22                   ` Nick Garnett
2003-03-19 18:26                     ` Gary Thomas
2003-03-19 18:52                       ` Nick Garnett
     [not found]                         ` <1048100525.7462.5617.camel@hermes.chez-thomas.org>
2003-03-19 19:21                           ` Nick Garnett
2003-03-20 13:02                           ` Nick Garnett
2003-03-20 13:14                             ` Gary Thomas
2003-03-20 18:11                               ` Nick Garnett

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=1047995318.7459.2925.camel@hermes.chez-thomas.org \
    --to=gary@mlbassoc.com \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=jld@ecoscentric.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).