GDB 6.1.1

GDB 6.1.1

[Andrew Cagney]

I suspect that there is going to be a GDB 6.1.1 (sometime in may), if 
nothing else to clean up some doco issues.   People should think about 
critical (i.e., crasher and build bug fixes) that should be committed to 
the branch.

Andrew

(yes I know I've not sent the announcement for 6.1, I've a logistic problem)

Re: GDB 6.1.1

[cgd]

At Tue, 13 Apr 2004 20:07:52 +0000 (UTC), "Andrew Cagney" wrote:
> I suspect that there is going to be a GDB 6.1.1 (sometime in may), if
> nothing else to clean up some doco issues.   People should think about
> critical (i.e., crasher and build bug fixes) that should be committed
> to the branch.

What is the policy (if any) for committing things to the branch?  Is
it documented anywhere?

(I looked on the mailing list and web pages, and didn't notice
anything, but i'll admit i didn't spend a *lot* of time looking...)



chris

Re: GDB 6.1.1

[Andrew Cagney]

http://sources.redhat.com/gdb/current/onlinedocs/gdbint_15.html#SEC133
15.2 Branch Commit Policy

The branch commit policy is pretty slack. GDB releases 5.0, 5.1 and 5.2 
all used the below:

     * 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 ;-)

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.

Re: GDB 6.1.1

[cgd]

At Tue, 11 May 2004 19:46:45 -0400, Andrew Cagney wrote:
> http://sources.redhat.com/gdb/current/onlinedocs/gdbint_15.html#SEC133
> 15.2 Branch Commit Policy

Thanks.

(I searched the mailing lists, but didn't think to look at the
internals manual!!  if i'd done the smart thing, i.e., googled for
"site:sources.redhat.com gdb branch policy" i would have found it
immediately, of course.  *sigh*)


cgd

Re: GDB 6.1.1

[Eli Zaretskii]

> From: cgd@broadcom.com
> Date: 11 May 2004 18:31:14 -0700
> 
> (I searched the mailing lists, but didn't think to look at the
> internals manual!!  if i'd done the smart thing, i.e., googled for
> "site:sources.redhat.com gdb branch policy" i would have found it
> immediately, of course.  *sigh*)

Actually, one should _first_ look in gdbint.info for such things, and
if not found there, complain loudly, so that the documentation is
improved for the next release.

Andrew puts a lot of effort into spelling out these issues in gdbint,
so we might as well use that ;-)