From: MFL Commissioner <mfl-commissioner@marino.st>
To: binutils@sourceware.org
Subject: Re: PATCH SET: DragonFly BSD, config.guess, and config.rpath
Date: Wed, 09 Mar 2011 05:10:00 -0000 [thread overview]
Message-ID: <4D770BCC.7030904@marino.st> (raw)
In-Reply-To: <201103082218.44673.vapier@gentoo.org>
On 3/9/2011 4:18 AM, Mike Frysinger wrote:
> On Tuesday, March 08, 2011 16:48:09 John Marino wrote:
>> 2011-03-08 John Marino<binutils@marino.st>
>>
>> * bfd/config.bfd: Add x86_64-*-dragonfly*, fix i386-*-dragonfly*
>> * bfd/configure.in: Delete unused bfd_elf32_i386_dragonfly_vec
>> * bfd/configure: Regenerate.
> changelog paths are relative to the file they go into. since these entries go
> into bfd/ChangeLog, the paths should be relative to that. so drop "bfd/" from
> all of these.
>
Okay, that was a mistake on my part. But can whoever commits this just
fix it on the fly? Is another set of file submissions really
necessary? (aimed at somebody that can commit these, not you Mike)
>> 3) config.guess.current.patch
>> 4) config.guess.221.patch
>> Pending GCC requirements, the preceding patches will update config.guess
>> to the last version defined by project/config. Use the following commit
>> message: 2011_MM_DD_changelog.guess.txt
>>
>>
>> 5) config.rpath.current.patch
>> 6) config.rpath.221.patch
>> Pending GCC requirements, the preceding patches will update config.guess
>> to the last version defined by project/gnulib. Use the following commit
>> message: 2011_MM_DD_changelog.repath.txt
> btw, when Ralf talked about gcc, he meant they should be submitted to gcc-
> patches@gcc.gnu.org first.
> -mike
Ok. That wasn't clear what he meant.
Regards,
John
next prev parent reply other threads:[~2011-03-09 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 21:53 John Marino
2011-03-09 3:18 ` Mike Frysinger
2011-03-09 5:10 ` MFL Commissioner [this message]
2011-03-12 7:38 ` MFL Commissioner
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=4D770BCC.7030904@marino.st \
--to=mfl-commissioner@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).