Date: Mon, 23 Jun 2003 07:50:02 +0300
From: "Eli Zaretskii" <eliz AT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-Id: <7458-Mon23Jun2003075001+0300-eliz@elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
Subject: [ac131313 AT redhat DOT com: GDB 6 branch created]
Reply-To: djgpp-workers AT delorie DOT com

FYI

------- Start of forwarded message -------
Mailing-List: contact gdb-help AT sources DOT redhat DOT com;
	run by ezmlm
Sender: gdb-owner AT sources DOT redhat DOT com
Date: Sun, 22 Jun 2003 23:43:07 -0400
From: Andrew Cagney <ac131313 AT redhat DOT com>
X-Accept-Language: en-us, en
To: gdb AT sources DOT redhat DOT com
Subject: GDB 6 branch created
X-PRIVAWALL-ID: 0002556710ac
X-OriginalArrivalTime: 23 Jun 2003 04:54:32.0309 (UTC) FILETIME=[89265A50:01C33943]

The GDB 6 branch (gdb_6_0-branch) has been created.

To check out this branch use something like:
$ cvs -z1 -d :pserver:anoncvs AT sources DOT redhat DOT 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



This message is processed by the PrivaWall Email Security Server. 
------- End of forwarded message -------