Re: [avr-libc-dev] Is there any active maintainer?

Am 22. Januar 2019 20:04:58 MEZ schrieb Taavo Raykoff : >Thanks. I will take some time and give this a shot. >I was thinking more along the lines of __malloc_lock and >__malloc_unlock hooks like you see in newlib. >Will keep you posted. >Taavo >___

Re: [avr-libc-dev] Is there any active maintainer?

Thanks. I will take some time and give this a shot. I was thinking more along the lines of __malloc_lock and __malloc_unlock hooks like you see in newlib. Will keep you posted. Taavo ___ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org

Re: [avr-libc-dev] Is there any active maintainer?

As Taavo Raykoff wrote: > What is the route to becoming an allowed committer — if I or someone > has time to help out with this? Given the low activity of all existing committers (including me), I'd say: enough dedication ... Regarding your malloc stuff: there is a testsuite in the source

Re: [avr-libc-dev] Is there any active maintainer?

As Taavo Raykoff wrote: > Is there any active maintainer on avr-libc? Depends on your definition of "active". I am the maintainer of it, but unfortunately, even though my activity is very low (being busy in many respects, family, job, German amateur radio league, other opensource stuff as

[avr-libc-dev] Is there any active maintainer?

Is there any active maintainer on avr-libc? I’d like to push a fix upstream. Thanks, Taavo ___ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/avr-libc-dev