--- Begin Message ---- From: Andrew Cagney <ac131313 at redhat dot com>
- To: gdb at sources dot redhat dot com
- Date: Sun, 22 Jun 2003 23:43:07 -0400
- Subject: GDB 6 branch created
- Delivery-date: Sun, 22 Jun 2003 23:53:00 -0400
- Envelope-to: cagney@gnu.org
The GDB 6 branch (gdb_6_0-branch) has been created.
To check out this branch use something like:
$ cvs -z1 -d :pserver:anoncvs@sources.redhat.com:/cvs/src co -r gdb_6_0-branch gdb+dejagnu
At present the release is scheduled for Sat August 02 (2003-08-02-gmt).http://www.gnu.org/software/gdb/schedule/(but at the time of writing the pages weren't yet up-to-date)
The branch commit policy is as follows:
- The `gdb/MAINTAINERS' file still holds.
- 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 `gdb/PROBLEMS' file is better than committing a hack.
- When considering a patch for the branch, suggested criteria include: Does it fix a build? Does it fix the sequence break main; run when debugging a static binary?
- The further a change is from the core of gdb, the less likely the change will worry anyone (e.g., target specific code).
- Only post a proposal to change the core of gdb after you've sent individual bribes to all the people listed in the `MAINTAINERS' file ;-)
- Only the very brave or very foolish would try to apply the obvious fix rule to the branch.
Andrew
--- End Message ---