Re: [patch] README: remove references to deleted remote-*.c

Re: [patch] README: remove references to deleted remote-*.c

[Michael Elizabeth Chastain]

mec> By the way, what happens to bugs reported to the mailing lists?
mec> Is anyone entering them into Gnats?

andrew> They dried up!  The power of documentation!

I still see legitimate bug reports in bug-gdb@gnu.org.

  http://mail.gnu.org/archive/html/bug-gdb/2003-01/index.html
    http://mail.gnu.org/archive/html/bug-gdb/2003-01/msg00004.html
    http://mail.gnu.org/archive/html/bug-gdb/2003-01/msg00009.html
    http://mail.gnu.org/archive/html/bug-gdb/2003-01/msg00010.html
    http://mail.gnu.org/archive/html/bug-gdb/2003-01/msg00008.html

These bug reports aren't going in to Gnats.  So they get whatever
service they get on the spot, and then we forget about them.

I still see plenty of spam in bug-gdb@gnu.org as well.

I wrote to bug-gdb-owner on 2002-12-29 offering to administer the list.
It's been more than a week and I've gotten nothing in return: no
acknowledgement, no nothing.

I would like gdb-gnats@sources.redhat.com to subscribe to
bug-gdb@gnu.org, so that bug reports from bug-gdb become part of
our official bug database.

I would like to remove all the spam from the bug-gdb@gnu.org.

Andrew and everybody, what are your thoughts?

Michael C

Re: [patch] README: remove references to deleted remote-*.c

[Andrew Cagney]

> mec> By the way, what happens to bugs reported to the mailing lists?
> mec> Is anyone entering them into Gnats?
> 
> andrew> They dried up!  The power of documentation!

Ok, I take that back.  There was a marked shift but not that dramatic. 
Looks like I've been un-subscribed.

> I still see legitimate bug reports in bug-gdb@gnu.org.
> 
>   http://mail.gnu.org/archive/html/bug-gdb/2003-01/index.html
>     http://mail.gnu.org/archive/html/bug-gdb/2003-01/msg00004.html
>     http://mail.gnu.org/archive/html/bug-gdb/2003-01/msg00009.html
>     http://mail.gnu.org/archive/html/bug-gdb/2003-01/msg00010.html
>     http://mail.gnu.org/archive/html/bug-gdb/2003-01/msg00008.html
> 
> These bug reports aren't going in to Gnats.  So they get whatever
> service they get on the spot, and then we forget about them.
> 
> I still see plenty of spam in bug-gdb@gnu.org as well.
> 
> I wrote to bug-gdb-owner on 2002-12-29 offering to administer the list.
> It's been more than a week and I've gotten nothing in return: no
> acknowledgement, no nothing.
> 
> I would like gdb-gnats@sources.redhat.com to subscribe to
> bug-gdb@gnu.org, so that bug reports from bug-gdb become part of
> our official bug database.

I've found people are largly co-operative if you ask them to submit the 
bug via the web interface.

If it really is still receiving much spam then that subscribe wouldn't 
help (and could possibly confuse things).  sware would bounce a bug 
submittion that @gnu.org had accepted, or sware would just end up full 
of spam reports.

Andrew

Re: [patch] README: remove references to deleted remote-*.c

[Elena Zannoni]

Michael Elizabeth Chastain writes:
 > mec> By the way, what happens to bugs reported to the mailing lists?
 > mec> Is anyone entering them into Gnats?
 > 
 > andrew> They dried up!  The power of documentation!
 > 
 > I still see legitimate bug reports in bug-gdb@gnu.org.
 > 
 >   http://mail.gnu.org/archive/html/bug-gdb/2003-01/index.html
 >     http://mail.gnu.org/archive/html/bug-gdb/2003-01/msg00004.html
 >     http://mail.gnu.org/archive/html/bug-gdb/2003-01/msg00009.html
 >     http://mail.gnu.org/archive/html/bug-gdb/2003-01/msg00010.html
 >     http://mail.gnu.org/archive/html/bug-gdb/2003-01/msg00008.html
 > 
 > These bug reports aren't going in to Gnats.  So they get whatever
 > service they get on the spot, and then we forget about them.
 > 
 > I still see plenty of spam in bug-gdb@gnu.org as well.

I thgought that at some point we created a new sources.redhat.com list
that recived the bug-gdb mail and filtered all the spam out. I don't
remember the name of the list, and I don't think I am subsrcibed to it
anymore, apparently.

I think the FSF policy is (was?) to not block spam.

Elena

 > 
 > I wrote to bug-gdb-owner on 2002-12-29 offering to administer the list.
 > It's been more than a week and I've gotten nothing in return: no
 > acknowledgement, no nothing.
 > 
 > I would like gdb-gnats@sources.redhat.com to subscribe to
 > bug-gdb@gnu.org, so that bug reports from bug-gdb become part of
 > our official bug database.
 > 
 > I would like to remove all the spam from the bug-gdb@gnu.org.
 > 
 > Andrew and everybody, what are your thoughts?
 > 
 > Michael C

Re: [patch] README: remove references to deleted remote-*.c

[Michael Elizabeth Chastain]

Well, I don't think we're going to fix this issue today,
so I ... filed a bug report on it.

Michael C
feeling overwhelmed

Re: [patch] README: remove references to deleted remote-*.c

[Michael Elizabeth Chastain]

Elena Z writes:
> I thgought that at some point we created a new sources.redhat.com list
> that recived the bug-gdb mail and filtered all the spam out. I don't
> remember the name of the list, and I don't think I am subsrcibed to it
> anymore, apparently.

I think that list is bug-gdb@sources.redhat.com:

  http://sources.redhat.com/ml/bug-gdb

I see spam copied over to that list.

Michael C

Re: [patch] README: remove references to deleted remote-*.c

[Michael Elizabeth Chastain]

Andrew C writes:
> Looks like I've been un-subscribed.

Ah, the power of randomness.  :)

> If it really is still receiving much spam then that subscribe wouldn't 
> help (and could possibly confuse things).  sware would bounce a bug 
> submittion that @gnu.org had accepted, or sware would just end up full 
> of spam reports.

bug-gdb is a mailman mailing list.  I would like to become a list
administrator and set it up to moderate the submissions, together
with a whitelist.  Then there would be zero spam, so it would be
safe to subscribe gdb-gnats to it.

Or we could find some other way to pull the reports in.  Or we could
just acknowledge that e-mail bug reports aren't collected into our
database (which I think is crummy).

Michael C

Re: [patch] README: remove references to deleted remote-*.c

[Andrew Cagney]

> Ah, you are referring to the bug reporting stuff, rather than
> the obsolete remote-*.c stuff.  I was a little mystified.
> 
> By the way, what happens to bugs reported to the mailing lists?
> Is anyone entering them into Gnats?

They dried up!  The power of documentation!

All N places which mention bug reports how recommend 
http://www.gnu.org/software/gdb/bugs/ in preference to the bug-gdb@ 
mailing list.

Andrew

Re: [patch] README: remove references to deleted remote-*.c

[Michael Elizabeth Chastain]

Ah, you are referring to the bug reporting stuff, rather than
the obsolete remote-*.c stuff.  I was a little mystified.

By the way, what happens to bugs reported to the mailing lists?
Is anyone entering them into Gnats?

Michael C

Re: [patch] README: remove references to deleted remote-*.c

[Andrew Cagney]

> Andrew C writes:
> 
>> Michael, check the bug database for some additional state on this.  The 
>> `correct fix' involves an addition to the documentation.
> 
> 
> I did some keyword searches and then read through the 574 open synopses.
> The closest I found was:
> 
>   PR gdb/685  remote-utils and remote-array obsolete
>   PR gdb/118  update remote protocol doco
> 
> These don't seem very close to me.

Sorry, I was thinking of this:
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=403

Andrew

Re: [patch] README: remove references to deleted remote-*.c

[Michael Elizabeth Chastain]

Andrew C writes:
> Michael, check the bug database for some additional state on this.  The 
> `correct fix' involves an addition to the documentation.

I did some keyword searches and then read through the 574 open synopses.
The closest I found was:

  PR gdb/685  remote-utils and remote-array obsolete
  PR gdb/118  update remote protocol doco

These don't seem very close to me.

Would you like me to revert the patch?  I thought it was obvious,
but maybe it's not.

Michael C

Re: [patch] README: remove references to deleted remote-*.c

[Andrew Cagney]

> This patch removes gdb/README references to deleted remote-*.c files.
> All these files are deleted, not just obsolete.
> 
> I noticed this while I was writing new text for the next section down,
> "Reporting Bugs in GDB".

Michael, check the bug database for some additional state on this.  The 
`correct fix' involves an addition to the documentation.

Andrew

[patch] README: remove references to deleted remote-*.c

[Michael Elizabeth Chastain]

This patch removes gdb/README references to deleted remote-*.c files.
All these files are deleted, not just obsolete.

I noticed this while I was writing new text for the next section down,
"Reporting Bugs in GDB".

Testing: I checked for ChangeLog entries about these file deletions.
I'm not failing to see them due to a CVS glitch or something.

I am committing this under the obvious fix rule.

Michael C

===

2003-01-05  Michael Chastain  <mec@shout.net>

	* README: Remove references to deleted remote-*.c files:
	remote-adapt.c, remote-eb.c, remote-mm.c, remote-nindy.c,
	remote-nrom.c, remote-os9k.c, remote-udi.c.

===

Index: README
===================================================================
RCS file: /cvs/src/src/gdb/README,v
retrieving revision 1.22
diff -u -r1.22 README
--- README	5 Sep 2002 12:13:08 -0000	1.22
+++ README	5 Jan 2003 16:47:49 -0000
@@ -449,38 +449,23 @@
    There are a number of remote interfaces for talking to existing ROM
 monitors and other hardware:
 
-	remote-adapt.c	 AMD 29000 "Adapt"
 	remote-array.c   Array Tech RAID controller
 	remote-e7000.c	 Hitachi E7000 ICE
-	remote-eb.c	 AMD 29000 "EBMON"
 	remote-es.c	 Ericsson 1800 monitor
 	remote-est.c	 EST emulator
 	remote-hms.c	 Hitachi Micro Systems H8/300 monitor
 	remote-mips.c	 MIPS remote debugging protocol
-	remote-mm.c	 AMD 29000 "minimon"
-	remote-nindy.c   Intel 960 "Nindy"
-	remote-nrom.c	 NetROM ROM emulator
-	remote-os9k.c	 PC running OS/9000
 	remote-rdi.c	 ARM with Angel monitor
 	remote-rdp.c	 ARM with Demon monitor
 	remote-sds.c	 PowerPC SDS monitor
 	remote-sim.c	 Generalized simulator protocol
 	remote-st.c	 Tandem ST-2000 monitor
-	remote-udi.c	 AMD 29000 using the AMD "Universal Debug Interface"
 	remote-vx.c	 VxWorks realtime kernel
 
    Remote-vx.c and the vx-share subdirectory contain a remote
 interface for the VxWorks realtime kernel, which communicates over TCP
 using the Sun RPC library.  This would be a useful starting point for
 other remote- via-ethernet back ends.
-
-   Remote-udi.c and the 29k-share subdirectory contain a remote
-interface for AMD 29000 programs, which uses the AMD "Universal Debug
-Interface".  This allows GDB to talk to software simulators,
-emulators, and/or bare hardware boards, via network or serial
-interfaces.  Note that GDB only provides an interface that speaks UDI,
-not a complete solution.  You will need something on the other end
-that also speaks UDI.
 
 
 Reporting Bugs in GDB