1) turned $Id: from m4 into texinfo comment

2) disabled @group where no longer supported by texinfo.tex

gdb/doc/gdb.alter-m4

@@ -1,6 +1,6 @@
 _dnl__ Copyright (c) 1988 1989 1990 1991 Free Software Foundation, Inc.
 _dnl__ This file is part of the source for the GDB manual.
-_dnl__ $Id$
+@c M4 FRAGMENT: $Id$
 @node Altering, _GDBN__ Files, Symbols, Top
 @chapter Altering Execution
 
@@ -138,8 +138,8 @@ The most common occasion to use the @code{jump} command is to back up,
 perhaps with more breakpoints set, over a portion of a program that has
 already executed, in order to examine its execution in more detail.
 
-@group
 @node Signaling, Returning, Jumping, Altering
+@c @group
 @section Giving the Program a Signal
 
 @table @code
@@ -157,7 +157,7 @@ signal.
 @code{signal} does not repeat when you press @key{RET} a second time
 after executing the command.
 @end table
-@end group
+@c @end group
 
 @node Returning, Calling, Signaling, Altering
 @section Returning from a Function

gdb/doc/gdb.cmds-m4

@@ -1,6 +1,6 @@
 _dnl__ Copyright (c) 1988 1989 1990 1991 Free Software Foundation, Inc.
 _dnl__ This file is part of the source for the GDB manual.
-_dnl__ $Id$
+@c M4 FRAGMENT: $Id$
 @node Commands, Running, Invocation, Top
 @chapter _GDBN__ Commands
 
@@ -107,7 +107,7 @@ all the sub-commands.
 @c FIXME: @pxref{Index} used to be here, but even though it shows up in
 @c FIXME...the 'aux' file with a pageno the xref can't find it.  
 
-@group
+@c @group
 @table @code
 @item info
 @kindex info
@@ -135,7 +135,7 @@ values, you can use @code{show} with no arguments; you may also use
 @c FIXME...program.  Ck w/ GNU: "info set" to be called something else,
 @c FIXME...or change desc of rule---eg "state of prog and debugging session"?
 @end table
-@end group
+@c @end group
 
 Here are three miscellaneous @code{show} subcommands, all of which are
 exceptional in lacking corresponding @code{set} commands:

gdb/doc/gdb.run-m4

@@ -1,7 +1,7 @@
 _dnl__								-*- Texinfo -*-
 _dnl__ Copyright (c) 1988 1989 1990 1991 Free Software Foundation, Inc.
 _dnl__ This file is part of the source for the GDB manual.
-_dnl__ $Id$
+@c M4 FRAGMENT: $Id$
 @node Running, Stopping, Commands, Top
 @chapter Running Programs Under _GDBN__
 
@@ -362,8 +362,8 @@ confirmation if you try to do either of these things; you can control
 whether or not you need to confirm by using the @code{set confirm} command
 (@pxref{Messages/Warnings}).
 
-@group
 @node Kill Process,  , Attach, Running
+@c @group
 @section Killing the Child Process
 
 @table @code
@@ -375,7 +375,7 @@ Kill the child process in which your program is running under _GDBN__.
 This command is useful if you wish to debug a core dump instead of a
 running process.  _GDBN__ ignores any core dump file while your program
 is running.
-@end group
+@c @end group
 
 On some operating systems, you can't execute your program in another
 process while breakpoints are active inside _GDBN__.  You can use the

gdb/doc/gdb.stop-m4

@@ -1,7 +1,7 @@
 _dnl__								-*- Texinfo -*-
 _dnl__ Copyright (c) 1988 1989 1990 1991 Free Software Foundation, Inc.
 _dnl__ This file is part of the source for the GDB manual.
-_dnl__ $Id$
+@c M4 FRAGMENT: $Id$
 @node Stopping, Stack, Running, Top
 @chapter Stopping and Continuing
 
@@ -877,7 +877,7 @@ number of a signal or its name (with or without the @samp{SIG} at the
 beginning).  The @var{keywords} say what change to make.
 @end table
 
-@group
+@c @group
 The keywords allowed by the @code{handle} command can be abbreviated.
 Their full names are:
 
@@ -905,7 +905,7 @@ and not handled.
 @item nopass
 _GDBN__ should not allow the program to see this signal.
 @end table
-@end group
+@c @end group
 
 When a signal has been set to stop the program, the program cannot see the
 signal until you continue.  It will see the signal then, if @code{pass} is