This is the mail archive of the ecos-patches@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Speed-up sprintf() family of functions.


On Wed, Jan 03, 2007 at 08:53:12AM +0100, Neundorf, Alexander wrote:
> 
> 
> > Von: ecos-patches-owner@ecos.sourceware.org
> > [mailto:ecos-patches-owner@ecos.sourceware.org]Im Auftrag von Sergei
> > Organov
> > 
> > Jonathan Larmour <jifl@eCosCentric.com> writes:
> > 
> > > Sergei Organov wrote:
> > >>>
> > >>>Oh yes, I know there's a lot of things I would do very differently
> > >>>given the chance and the benefit of 10 more years of 
> > experience. There
> > >>>are many, many places the code could be improved (or 
> > rewritten!), and
> > >>>that is one.
> > 
> > Does anybody actually work on improving those things? From outside it
> > looks like kernel and libc development is stopped.
> 

> IMO an experimental/3rd party branch or repository would be a good
> idea for eCos, where it is easy to get write access and where new
> and experimental stuff can be committed, tested and developed. Right
> now if I have something new I can't send a patch before it's ready
> for production use, which is against "release early, release often"
> and which makes it harder to work on something with somebody else
> who is interested in it.

First off, you can send a patch, just make it clear its for comments
only, not for production use or to be merged into the repository. If
you want use bugzilla and attach the patch there.

What i have also done in the past is setup my own CVS server for
packages which are under development by multiple developers. Once the
code was complete and production quality it was then merged into the
anoncvs repository. 

        Andrew


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]