public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: binutils@sources.redhat.com
Subject: Re: binutils-2.16 news
Date: Wed, 20 Apr 2005 09:38:00 -0000	[thread overview]
Message-ID: <426622C5.5090109@redhat.com> (raw)
In-Reply-To: <s26615f8.034@emea1-mh.id2.novell.com>

Hi Jan,

> As far as I remember either you or Nick or Ian provided me with a list of 
 > targets one would ideally test against when making changes of global 
effect.
 > Quite a number of these are listed here.

Note - those lists of targets were intended to cover the vast majority 
of targets supported by binutils, even those without maintainers.  The 
intention was to make sure that global changes did not break anything, 
even unmaintained ports.

> I thus wonder whether there isn't (and if not, couldn't be) a place where 
 > a list of "primary" targets is maintained (which should clearly be free
 > of targets already deprecated),

This could be deduced from the list of maintainers in the 
binutils/MAINTAINERS file.

Cheers
   Nick




  reply	other threads:[~2005-04-20  9:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20  7:42 Jan Beulich
2005-04-20  9:38 ` Nick Clifton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-20  7:15 Alan Modra
2005-04-20  8:45 ` Ralf Corsepius
2005-04-20  9:40   ` Nick Clifton
2005-04-20 10:15     ` Ralf Corsepius
2005-04-20 14:15       ` Nick Clifton
2005-04-21  3:20       ` Alan Modra
2005-04-21  3:49         ` Ralf Corsepius
2005-04-21  4:19           ` Daniel Jacobowitz
2005-04-22 11:36       ` Joel Sherrill <joel@OARcorp.com>

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=426622C5.5090109@redhat.com \
    --to=nickc@redhat.com \
    --cc=JBeulich@novell.com \
    --cc=binutils@sources.redhat.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).