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]

profiling patch ping


Is there something wrong with this patch?

Not important enough?

I don't want to nag, but it would be helpful to know at which point
I should assume "communication by default", i.e. that nobody responded
because it is of no interest to any maintainer in particular or that
it was "not even wrong"...

http://sourceware.org/ml/ecos-patches/2008-10/msg00007.html

I don't need this committed to CVS as such, I always have half a dozen
modifications to eCos repository at any moment in time and that works
great. Open source is neat that way. Only the modifications of interest
to the community are actually committed. The rest can stay in local
snapshots of repositories(sometimes even project specific or
even development branch specific), but it is nice to keep it to half
a dozen over time(i.e. that some patches get committed
occasionally).

-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer


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