From: Nick Clifton <nickc@redhat.com>
To: "Richard Earnshaw (home)" <richard.earnshaw@buzzard.freeserve.co.uk>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"aph@redhat.com" <aph@redhat.com>
Subject: Re: RFC: Collecting together binary file attributes into a single file.
Date: Thu, 29 Sep 2011 14:14:00 -0000 [thread overview]
Message-ID: <4E847BFD.1000807@redhat.com> (raw)
In-Reply-To: <7466E409-8C17-408C-82C6-E0A1C6AD3D20@buzzard.freeserve.co.uk>
Hi Richard,
> I don't think it's a good idea to have the attributes of
> every CPU we support in a single file. That's going to
> get unmaintainable very quickly.
Really - why ?
These attributes are mostly static. Some new ones might be added from
time to time, but baring the introduction of new ports I do not see any
other changes that re likely to happen.
Cheers
Nick
next prev parent reply other threads:[~2011-09-29 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 9:38 Nick Clifton
2011-09-29 10:12 ` Richard Earnshaw (home)
2011-09-29 14:14 ` Nick Clifton [this message]
2011-09-29 17:57 ` Joseph S. Myers
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=4E847BFD.1000807@redhat.com \
--to=nickc@redhat.com \
--cc=aph@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=richard.earnshaw@buzzard.freeserve.co.uk \
/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