From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 12605 invoked from network); 24 May 2020 02:53:18 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 24 May 2020 02:53:18 -0000 Received: (qmail 15860 invoked by uid 550); 24 May 2020 02:53:13 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 15830 invoked from network); 24 May 2020 02:53:12 -0000 Date: Sat, 23 May 2020 22:53:00 -0400 From: Rich Felker To: musl@lists.openwall.com Message-ID: <20200524025259.GM1079@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [musl] 1.1.x branch possibility When releasing 1.2.0, I left open the possibility of further releases in a 1.1.x branch. The libc.threads_minus_1 lock skipping bug is the first thing to come up that's really big enough to motivate actually doing such a branch. In practice fairly little is likely to hit it in practice, but it's enough of an unknown and potential blow-up that we need to advise patching or upgrade. Aside from that, there were possibly arch-specific regressions in 1.1.24 on mips, and a few other arch-specific bugs that had been around for a few release cycles. These would make sense to fix in a 1.1.25, if we do it.