From: Philip Blundell <pb@nexus.co.uk>
To: binutils@sources.redhat.com, Hans-Peter Nilsson <hp@bitrange.com>,
"H . J . Lu" <hjl@lucon.org>
Subject: Re: Release 2.12
Date: Thu, 25 Oct 2001 01:56:00 -0000 [thread overview]
Message-ID: <E15wgGJ-0007OQ-00@mill.nexus.co.uk> (raw)
In-Reply-To: <20011025121333.D1037@bubble.sa.bigpond.net.au>
>The real question here is "why don't debian and hard hat use FSF
>binutils releases in preference to HJ's releases?"
Because, pretty clearly, FSF releases are still not happening often enough;
bugs don't get fixed in a timely fashion.
Having thought about the matter a bit in recent weeks, I think a release every
two or three months would probably be about right, with maybe a patch version
or two in the interim. They need to be seldom enough for a reasonable amount
of testing to go on -- distributions like Red Hat and Debian could probably
tolerate more instability, because they do their own QA, but for individual
users, particularly on slightly obscure platforms, it will take some care to
make sure that each release doesn't just end up swapping one bug-of-the-day for
another.
p.
next prev parent reply other threads:[~2001-10-25 1:56 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 18:26 Hans-Peter Nilsson
2001-10-24 18:38 ` Alan Modra
2001-10-24 18:43 ` David O'Brien
2001-10-24 19:30 ` Alan Modra
2001-10-24 19:35 ` MMIX (was: Re: Release 2.12) Hans-Peter Nilsson
2001-10-24 21:45 ` Release 2.12 Eric Christopher
2001-10-25 8:41 ` H . J . Lu
2001-10-25 8:47 ` H . J . Lu
2001-10-24 18:49 ` Daniel Jacobowitz
2001-10-24 19:43 ` Alan Modra
2001-10-24 20:10 ` Daniel Jacobowitz
2001-10-24 20:35 ` Alan Modra
2001-10-24 20:44 ` Daniel Jacobowitz
2001-10-25 5:09 ` Christopher C. Chimelis
2001-10-25 1:56 ` Philip Blundell [this message]
2001-10-25 8:30 ` H . J . Lu
2001-10-25 8:47 ` David O'Brien
[not found] ` <amodra@bigpond.net.au>
2002-01-04 17:42 ` [Linux-ia64] Compiling kernel 2.4.17 fails at link stage Grant Grundler
2002-01-04 17:59 ` H . J . Lu
2002-01-04 20:37 ` Grant Grundler
2002-01-04 22:39 ` H . J . Lu
2002-01-07 12:52 ` Grant Grundler
2002-01-04 19:21 ` Alan Modra
2003-11-29 2:33 ` ppc problem with .rodata.str1.4. binutils requirement for gcc 3.3.1? David Edelsohn
2003-11-29 3:05 ` Alan Modra
2003-11-29 4:06 ` David Edelsohn
2003-11-29 4:10 ` Andrew Pinski
2003-11-29 4:20 ` David Edelsohn
2003-11-29 6:47 ` Alan Modra
2003-11-29 19:40 ` David Edelsohn
2004-05-19 15:19 ` Powerpc Linux build fails David Edelsohn
2004-05-20 0:39 ` Alan Modra
2004-05-20 1:24 ` Alan Modra
2004-05-20 1:46 ` Alan Modra
2004-05-20 2:29 ` David Edelsohn
2004-05-20 3:10 ` Alan Modra
2006-08-04 1:49 ` Link problems with section anchors David Edelsohn
2006-08-04 2:04 ` Alan Modra
2001-10-24 19:37 ` Release 2.12 Russ Allbery
2001-10-24 19:52 ` Alan Modra
2001-10-25 0:46 ` H . J . Lu
2001-10-25 8:57 ` David O'Brien
2001-10-25 9:38 ` H . J . Lu
2001-10-25 9:44 ` H . J . Lu
2001-12-31 19:09 Compiling kernel 2.4.17 fails at link stage Krishnakumar B
2002-01-04 3:50 ` Alan Modra
2002-01-04 12:39 ` [Linux-ia64] " Alan Modra
[not found] <087e01c3b5da$77d658e0$0202040a@catdog>
2003-11-29 1:42 ` ppc problem with .rodata.str1.4. binutils requirement for gcc 3.3.1? Alan Modra
2003-11-29 18:14 ` Kris Warkentin
[not found] <3A3FC75F7C72D711A7DC009027AC9C4B1788D9@jupiter>
2004-05-19 3:30 ` Powerpc Linux build fails Alan Modra
2004-05-19 4:27 ` Geoff Keating
2004-05-19 5:10 ` Alan Modra
2004-05-19 16:24 ` Kumar Gala
2004-05-20 0:44 ` Alan Modra
[not found] <44D2755E.9020600@us.ibm.com>
2006-08-04 1:30 ` Link problems with section anchors Alan Modra
2006-08-04 9:04 ` Richard Sandiford
2006-08-04 13:53 ` Steven Munroe
2006-08-04 13:54 ` David Edelsohn
2006-08-04 14:01 ` Richard Sandiford
2006-08-04 14:12 ` David Edelsohn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E15wgGJ-0007OQ-00@mill.nexus.co.uk \
--to=pb@nexus.co.uk \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=hp@bitrange.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).