GDB 6.3 branch available

GDB 6.3 branch available

[Andrew Cagney]

Hello,

The gdb_6_3-branch has been created and is now available for testing and 
late breaking fixes.  The branch commit policy is:

@itemize @bullet
@item
The @file{gdb/MAINTAINERS} file still holds.
@item
Don't fix something on the branch unless/until it is also fixed in the
trunk.  If this isn't possible, mentioning it in the @file{gdb/PROBLEMS}
file is better than committing a hack.
@item
When considering a patch for the branch, suggested criteria include:
Does it fix a build?  Does it fix the sequence @kbd{break main; run}
when debugging a static binary?
@item
The further a change is from the core of @value{GDBN}, the less likely
the change will worry anyone (e.g., target specific code).
@item
Only post a proposal to change the core of @value{GDBN} after you've
sent individual bribes to all the people listed in the
@file{MAINTAINERS} file @t{;-)}
@end itemize

@emph{Pragmatics: Provided updates are restricted to non-core
functionality there is little chance that a broken change will be fatal.
This means that changes such as adding a new architectures or (within
reason) support for a new host are considered acceptable.}

Andrew

Re: GDB 6.3 branch available

[Andrew Cagney]

[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]

PS: Forgot to attach the relevant patches.  Note that mainline is now 
6.3.50.

-

Andrew Cagney wrote:
> Hello,
> 
> The gdb_6_3-branch has been created and is now available for testing and 
> late breaking fixes.  The branch commit policy is:
> 
> @itemize @bullet
> @item
> The @file{gdb/MAINTAINERS} file still holds.
> @item
> Don't fix something on the branch unless/until it is also fixed in the
> trunk.  If this isn't possible, mentioning it in the @file{gdb/PROBLEMS}
> file is better than committing a hack.
> @item
> When considering a patch for the branch, suggested criteria include:
> Does it fix a build?  Does it fix the sequence @kbd{break main; run}
> when debugging a static binary?
> @item
> The further a change is from the core of @value{GDBN}, the less likely
> the change will worry anyone (e.g., target specific code).
> @item
> Only post a proposal to change the core of @value{GDBN} after you've
> sent individual bribes to all the people listed in the
> @file{MAINTAINERS} file @t{;-)}
> @end itemize
> 
> @emph{Pragmatics: Provided updates are restricted to non-core
> functionality there is little chance that a broken change will be fatal.
> This means that changes such as adding a new architectures or (within
> reason) support for a new host are considered acceptable.}
> 
> Andrew
> 


[-- Attachment #2: diffs-mainline --]
[-- Type: text/plain, Size: 458 bytes --]

2004-10-19  Andrew Cagney  <cagney@gnu.org>

	GDB 6.3 branch created.
	* version.in: Bump to version 6.3.50_2004-10-19-cvs.

Index: version.in
===================================================================
RCS file: /cvs/src/src/gdb/version.in,v
retrieving revision 1.1199
diff -p -u -r1.1199 version.in
--- version.in	19 Oct 2004 00:00:02 -0000	1.1199
+++ version.in	19 Oct 2004 18:16:53 -0000
@@ -1 +1 @@
-6.2.50_2004-10-19-cvs
+6.3.50_2004-10-19-cvs

[-- Attachment #3: diffs-branch --]
[-- Type: text/plain, Size: 443 bytes --]

2004-10-19  Andrew Cagney  <cagney@gnu.org>

	GDB 6.3 branch created.
	* version.in: Bump to version 6.2.90.

Index: version.in
===================================================================
RCS file: /cvs/src/src/gdb/version.in,v
retrieving revision 1.1198
diff -p -u -r1.1198 version.in
--- version.in	18 Oct 2004 00:00:02 -0000	1.1198
+++ version.in	19 Oct 2004 18:17:01 -0000
@@ -1 +1 @@
-6.2.50_2004-10-18-cvs
+6.2.90_2004-10-19-cvs