musl mailing list

Follow @Openwall on Twitter for new release announcements and other news

musl mailing list

	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2025	47	91	83	48	70	160
2024	107	179	271	101	92	160	73	159	57	74	52	70
2023	47	160	92	74	291	120	110	48	47	51	56	36
2022	118	105	86	106	95	99	61	95	190	99	71	45
2021	111	71	58	79	98	37	92	121	57	104	61	95
2020	257	161	127	206	128	173	87	138	134	191	134	106
2019	130	206	136	63	66	147	167	119	159	131	76	113
2018	151	124	101	119	84	98	128	68	171	49	105	81
2017	164	89	112	104	69	257	132	127	68	91	140	101
2016	215	166	385	167	101	182	87	78	123	147	69	82
2015	165	165	193	261	278	235	178	179	159	212	150	87
2014	88	88	142	243	178	203	303	346	198	188	227	138
2013	179	162	158	244	121	133	267	205	102	81	144	123
2012	25	47	72	105	165	305	142	411	234	199	150	142
2011				64	46	73	117	159	30	30	11

Recent messages:

2025/06/23 #1: Re: Bug in reallocf(3) when calling realloc(3) (Rich Felker <dalias@...c.org>)
2025/06/22 #1: Re: Bug in reallocf(3) when calling realloc(3) (Florian Weimer <fweimer@...hat.com>)
2025/06/21 #21: Re: Bug in reallocf(3) when calling realloc(3) (Alejandro Colomar <alx@...nel.org>)
2025/06/21 #20: Re: Bug in reallocf(3) when calling realloc(3) (Rich Felker <dalias@...c.org>)
2025/06/21 #19: Bug in reallocf(3) when calling realloc(3) (Alejandro Colomar <alx@...nel.org>)
2025/06/21 #18: Re: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Rich Felker <dalias@...c.org>)
2025/06/21 #17: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/21 #16: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Adhemerval Zanella <adhemerval.zanella@...aro.org>)
2025/06/21 #15: Re: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Markus Wichmann <nullplan@....net>)
2025/06/21 #14: alx-0029r2 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
2025/06/21 #13: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Sam James <sam@...too.org>)
2025/06/21 #12: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/21 #11: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
2025/06/21 #10: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Sam James <sam@...too.org>)
2025/06/21 #9: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Paul Eggert <eggert@...ucla.edu>)
2025/06/21 #8: Re: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
2025/06/21 #7: Re: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Rich Felker <dalias@...c.org>)
2025/06/21 #6: Re: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Rich Felker <dalias@...c.org>)
2025/06/21 #5: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
2025/06/21 #4: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
2025/06/21 #3: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
2025/06/21 #2: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Paul Eggert <eggert@...ucla.edu>)
2025/06/21 #1: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
2025/06/20 #17: Re: alx-0029r1 - Restore the traditional realloc(3) specification ("Maciej W. Rozycki" <macro@...hat.com>)
2025/06/20 #16: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Christopher Bazley <chris.bazley.wg14@...il.com>)
2025/06/20 #15: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Thorsten Glaser <tg@...bsd.de>)
2025/06/20 #14: Re: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
2025/06/20 #13: alx-0029r1 - Restore the traditional realloc(3) specification (Alejandro Colomar <alx@...nel.org>)
2025/06/20 #12: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Paul Eggert <eggert@...ucla.edu>)
2025/06/20 #11: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/20 #10: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Eric Blake <eblake@...hat.com>)
2025/06/20 #9: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Joseph Myers <josmyers@...hat.com>)
2025/06/20 #8: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Mark Harris <mark.hsj@...il.com>)
2025/06/20 #7: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/20 #6: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Vincent Lefevre <vincent@...c17.net>)
2025/06/20 #5: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/20 #4: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Vincent Lefevre <vincent@...c17.net>)
2025/06/20 #3: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Paul Eggert <eggert@...ucla.edu>)
2025/06/20 #2: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Vincent Lefevre <vincent@...c17.net>)
2025/06/20 #1: Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
2025/06/19 #21: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/19 #20: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/19 #19: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/19 #18: Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Thorsten Glaser <tg@...bsd.de>)
2025/06/19 #17: Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
2025/06/19 #16: Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Eric Blake <eblake@...hat.com>)
2025/06/19 #15: Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Eric Blake <eblake@...hat.com>)
2025/06/19 #14: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Eric Blake <eblake@...hat.com>)
2025/06/19 #13: Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Thorsten Glaser <tg@...bsd.de>)
2025/06/19 #12: Re: [v2] malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
2025/06/19 #11: [v2] malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
2025/06/19 #10: Re: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
2025/06/19 #9: Re: malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
2025/06/19 #8: Re: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
2025/06/19 #7: Re: malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
2025/06/19 #6: Re: malloc.3: Clarify realloc(3) standards conformance (Vincent Lefevre <vincent@...c17.net>)
2025/06/19 #5: Re: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
2025/06/19 #4: Re: malloc.3: Clarify realloc(3) standards conformance (Rich Felker <dalias@...c.org>)
2025/06/19 #3: Re: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
2025/06/19 #2: Re: malloc.3: Clarify realloc(3) standards conformance (Collin Funk <collin.funk1@...il.com>)
2025/06/19 #1: malloc.3: Clarify realloc(3) standards conformance (Alejandro Colomar <alx@...nel.org>)
2025/06/18 #16: Re: Planned locale work and community thoughts (Rich Felker <dalias@...c.org>)
2025/06/18 #15: Re: Planned locale work and community thoughts (Thorsten Glaser <tg@...bsd.de>)
2025/06/18 #14: Re: Planned locale work and community thoughts (Rich Felker <dalias@...c.org>)
2025/06/18 #13: Re: Planned locale work and community thoughts (Rich Felker <dalias@...c.org>)
2025/06/18 #12: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/18 #11: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/18 #10: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Rich Felker <dalias@...c.org>)
2025/06/18 #9: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
2025/06/18 #8: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Andreas Schwab <schwab@...e.de>)
2025/06/18 #7: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Thorsten Glaser <tg@...bsd.de>)
2025/06/18 #6: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
2025/06/18 #5: Re: [PATCH] LoongArch64: add new reloc types and NT_LOONGARCH_HW_* into elf.h (lixing <lixing@...ngson.cn>)
2025/06/18 #4: Re: [PATCH] LoongArch64: add new reloc types and NT_LOONGARCH_HW_* into elf.h (Yao Zi <ziyao@...root.org>)
2025/06/18 #3: Re: [PATCH] LoongArch64: add new reloc types and NT_LOONGARCH_HW_* into elf.h (Rich Felker <dalias@...c.org>)
2025/06/18 #2: Re: [PATCH] time.h: drop non-standard and out-of-date CLOCK_SGI_CYCLE (Yao Zi <ziyao@...root.org>)
2025/06/18 #1: Re: [PATCH] LoongArch64: add new reloc types and NT_LOONGARCH_HW_* into elf.h (Yao Zi <ziyao@...root.org>)
2025/06/17 #9: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/17 #8: Re[2]: Re: BUG: realloc(p,0) should be consistent with malloc(0) ("Laurent Bercot" <ska-dietlibc@...rnet.org>)
2025/06/17 #7: Re[2]: Re: BUG: realloc(p,0) should be consistent with malloc(0) ("Laurent Bercot" <ska-dietlibc@...rnet.org>)
2025/06/17 #6: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Rich Felker <dalias@...c.org>)
2025/06/17 #5: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
2025/06/17 #4: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Paul Eggert <eggert@...ucla.edu>)
2025/06/17 #3: Re: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Rich Felker <dalias@...c.org>)
2025/06/17 #2: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Florian Weimer <fweimer@...hat.com>)
2025/06/17 #1: Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
2025/06/16 #13: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Joseph Myers <josmyers@...hat.com>)
2025/06/16 #12: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/16 #11: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/16 #10: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/16 #9: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/16 #8: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Adhemerval Zanella Netto <adhemerval.zanella@...aro.org>)
2025/06/16 #7: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Florian Weimer <fweimer@...hat.com>)
2025/06/16 #6: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Adhemerval Zanella Netto <adhemerval.zanella@...aro.org>)
2025/06/16 #5: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Paul Eggert <eggert@...ucla.edu>)
2025/06/16 #4: Re: BUG: realloc(p,0) should be consistent with malloc(0) (enh <enh@...gle.com>)
2025/06/16 #3: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/16 #2: Re: BUG: realloc(p,0) should be consistent with malloc(0) (Rich Felker <dalias@...c.org>)
2025/06/16 #1: BUG: realloc(p,0) should be consistent with malloc(0) (Alejandro Colomar <alx@...nel.org>)
2025/06/15 #2: Re: On current (and future) use of LCTRANS (Rich Felker <dalias@...c.org>)

22120 messages

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.