From: "David O'Brien" <obrien@NUXI.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: binutils@sourceware.cygnus.com
Subject: Re: GAS copyright update
Date: Wed, 03 May 2000 12:49:00 -0000 [thread overview]
Message-ID: <20000503124929.A98199@dragon.nuxi.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0005031639290.10857-100000@front.linuxcare.com.au>
On Wed, May 03, 2000 at 04:40:21PM +1000, Alan Modra wrote:
> Applied. Release branch too.
I looked at the website, but didn't see the branching/release paradigm
Binutils uses (ie, FreeBSD has both a -CURRENT (trunk) and multiple
-STABLE branches (RELENG_{4,3,22}). Features enter on the trunk and only
if highly tested and stable can they even be candidates for committing to
a -STABLE branch. Users expect -STABLE branches to change slowly, so
many things that could be back ported aren't to keep from disturbing
deployed servers.
Can you take a moment and explain it?
I am in the process of updating FreeBSD's Binutils. Typically I only use
released code for contributed code. However as you know the latest
Binutils release is 1.5 years old. I now have to figure out what to
import from anoncvs or an FTP'ed snapshot (and what date is a stable
Binutils). A requirement in FreeBSD's Binutils upgrade is IA-64 support.
--
-- David (obrien@NUXI.com)
next prev parent reply other threads:[~2000-05-03 12:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-02 19:42 David O'Brien
2000-05-02 23:41 ` Alan Modra
2000-05-03 12:49 ` David O'Brien [this message]
2000-05-03 12:56 ` Ian Lance Taylor
2000-05-03 12:57 ` Ian Lance Taylor
2000-05-04 2:04 ` Philip Blundell
2000-05-04 10:50 ` David O'Brien
2000-05-04 11:16 ` Philip Blundell
2000-05-04 11:36 ` David O'Brien
2000-05-04 11:44 ` Philip Blundell
2000-05-04 12:07 ` David O'Brien
2000-05-04 12:16 ` Ian Lance Taylor
[not found] ` <obrien@NUXI.com>
[not found] ` <E13KpFp-0000sK-00@kings-cross.london.uk.eu.org>
2000-10-11 16:27 ` A bugfix from last month for 2.10.1? David O'Brien
2000-10-14 4:11 ` Philip Blundell
2000-05-03 12:10 ` GAS copyright update Geoff Keating
2000-05-03 12:27 ` Ian Lance Taylor
2000-07-23 14:10 A bugfix from last month for 2.10.1? Michael Sokolov
2000-08-04 14:19 ` Philip Blundell
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=20000503124929.A98199@dragon.nuxi.com \
--to=obrien@nuxi.com \
--cc=alan@linuxcare.com.au \
--cc=binutils@sourceware.cygnus.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).