From: Mike Frysinger <vapier@gentoo.org>
To: John Marino <binutils@marino.st>
Cc: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>, binutils@sourceware.org
Subject: Re: PATCH: Fix support for DragonFly BSD on binutils 2.21 and trunk
Date: Tue, 08 Mar 2011 20:10:00 -0000 [thread overview]
Message-ID: <AANLkTin1WtyNJhK19ArrEO_vPdXhSDtMXHJHjaq_ZQpm@mail.gmail.com> (raw)
In-Reply-To: <4D768774.8090507@marino.st>
On Tue, Mar 8, 2011 at 2:45 PM, John Marino wrote:
> Wouldn't people want the very latest config.guess in place before branching?
> I'm primarily concerned with getting binutils 2.51 fixed before it's next
> release (I saw it went into beta today?)
eh ? there is no binutils-2.51. i'm guessing you're talking about
hjlu's binutils 2.xx.51.xx "releases". he doesnt do actual
"releases", he simply does snapshots of the latest cvs head and adds
his own set of patches on top of it. there is no "alpha" or "beta" or
anything else with his releases. they also have no impact on the
release process of the gnu binutils (which are versioned x.y or
x.y.z).
-mike
next prev parent reply other threads:[~2011-03-08 20:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 18:14 John Marino
2011-03-08 18:25 ` Mike Frysinger
2011-03-08 18:42 ` John Marino
2011-03-08 19:11 ` Mike Frysinger
2011-03-08 18:54 ` Mike Frysinger
2011-03-08 18:58 ` John Marino
2011-03-08 19:09 ` Mike Frysinger
2011-03-08 19:30 ` John Marino
2011-03-08 19:39 ` MFL Commissioner
2011-03-08 19:43 ` Ralf Wildenhues
2011-03-08 19:50 ` John Marino
2011-03-08 20:01 ` Ralf Wildenhues
2011-03-08 20:09 ` John Marino
2011-03-08 20:16 ` Mike Frysinger
2011-03-08 20:16 ` Ralf Wildenhues
2011-03-08 20:10 ` Mike Frysinger [this message]
2011-03-08 20:15 ` John Marino
2011-03-08 20:21 ` Mike Frysinger
2011-03-08 19:51 ` Mike Frysinger
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=AANLkTin1WtyNJhK19ArrEO_vPdXhSDtMXHJHjaq_ZQpm@mail.gmail.com \
--to=vapier@gentoo.org \
--cc=Ralf.Wildenhues@gmx.de \
--cc=binutils@marino.st \
--cc=binutils@sourceware.org \
/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).