Any documentation about how uClibc would like new architecture patches?

Mike Frysinger vapier at
Sat Jan 5 09:31:09 UTC 2008

On Thursday 25 October 2007, Hans-Christian Egtvedt wrote:
> I am in the work of submitting the AVR32 architecture fork of uClibc,
> and would like to know if you have a preferd way of receiving the
> patches?
> My plan is to pull down the latest snapshot, do a merge in my local
> repository (for the record I use git), test and verify that it works as
> intended and then submit patches.
> I was planning on splitting the patches into ldso.patch, libc.patch and
> libpthread.patch. Or is a huge patch ok?
> The total size of the diff is 99316 bytes, 3582 lines.

it's already been done, but all patches should be posted to the list.  i guess 
a more "developer guide" page on the website is in order ...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
Url : 

More information about the uClibc mailing list