* mail to MAXQ maintainer is bouncing
@ 2006-10-24 8:50 Ben Elliston
2006-11-09 18:02 ` Nick Clifton
0 siblings, 1 reply; 4+ messages in thread
From: Ben Elliston @ 2006-10-24 8:50 UTC (permalink / raw)
To: binutils
If we cannot track Inderpreet down on the mailing list, perhaps we
need to find a new maintainer for MAXQ?
Ben
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: mail to MAXQ maintainer is bouncing
2006-10-24 8:50 mail to MAXQ maintainer is bouncing Ben Elliston
@ 2006-11-09 18:02 ` Nick Clifton
2006-11-09 20:58 ` Ben Elliston
0 siblings, 1 reply; 4+ messages in thread
From: Nick Clifton @ 2006-11-09 18:02 UTC (permalink / raw)
To: Ben Elliston, inderpreetb; +Cc: binutils
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
Hi Ben,
> If we cannot track Inderpreet down on the mailing list, perhaps we
> need to find a new maintainer for MAXQ?
Agreed.
In the meantime, unless someone comes forward, I propose applying the
attached patch to mark the MAXQ port as obsolete. (The patch also
removes support for the previously obsoleted targets).
Any objections to my applying this patch ?
Cheers
Nick
[-- Attachment #2: config.bfd.patch --]
[-- Type: text/x-patch, Size: 1121 bytes --]
Index: bfd/config.bfd
===================================================================
RCS file: /cvs/src/src/bfd/config.bfd,v
retrieving revision 1.217
diff -c -3 -p -r1.217 config.bfd
*** bfd/config.bfd 25 Oct 2006 06:49:20 -0000 1.217
--- bfd/config.bfd 9 Nov 2006 17:57:04 -0000
*************** targ_underscore=no
*** 31,42 ****
# Catch obsolete configurations.
case $targ in
! m68*-apple-aux* | \
! m68*-apollo-* | \
! m68*-bull-sysv* | \
! m68*-*-rtemscoff* | \
! i960-*-rtems* | \
! or32-*-rtems* | \
null)
if test "x$enable_obsolete" != xyes; then
echo "*** Configuration $targ is obsolete." >&2
--- 31,37 ----
# Catch obsolete configurations.
case $targ in
! maxq-*-coff | \
null)
if test "x$enable_obsolete" != xyes; then
echo "*** Configuration $targ is obsolete." >&2
*************** case $targ in
*** 48,53 ****
--- 43,54 ----
esac
case $targ in
+ m68*-apple-aux* | \
+ m68*-apollo-* | \
+ m68*-bull-sysv* | \
+ m68*-*-rtemscoff* | \
+ i960-*-rtems* | \
+ or32-*-rtems* | \
m68*-*-lynxos* | \
sparc-*-lynxos* | \
vax-*-vms* | \
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: mail to MAXQ maintainer is bouncing
2006-11-09 18:02 ` Nick Clifton
@ 2006-11-09 20:58 ` Ben Elliston
2006-11-10 7:54 ` Nick Clifton
0 siblings, 1 reply; 4+ messages in thread
From: Ben Elliston @ 2006-11-09 20:58 UTC (permalink / raw)
To: Nick Clifton; +Cc: inderpreetb, binutils
Hi Nick
> In the meantime, unless someone comes forward, I propose applying the
> attached patch to mark the MAXQ port as obsolete. (The patch also
> removes support for the previously obsoleted targets).
>
> Any objections to my applying this patch ?
Seems reasonable to me.
Ben
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: mail to MAXQ maintainer is bouncing
2006-11-09 20:58 ` Ben Elliston
@ 2006-11-10 7:54 ` Nick Clifton
0 siblings, 0 replies; 4+ messages in thread
From: Nick Clifton @ 2006-11-10 7:54 UTC (permalink / raw)
To: binutils
Hi Guys,
>> In the meantime, unless someone comes forward, I propose applying the
>> attached patch to mark the MAXQ port as obsolete. (The patch also
>> removes support for the previously obsoleted targets).
I have now applied this patch.
Cheers
Nick
bfd/ChangeLog
2006-11-10 Nick Clifton <nickc@redhat.com>
* config.bfd: Move previously obsoleted targets to the REMOVED
list.
Add maxq-*-coff to the obsolete list.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-11-10 7:54 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-10-24 8:50 mail to MAXQ maintainer is bouncing Ben Elliston
2006-11-09 18:02 ` Nick Clifton
2006-11-09 20:58 ` Ben Elliston
2006-11-10 7:54 ` Nick Clifton
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).