From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: Re: GDB 6.3 branch available
Date: Tue, 19 Oct 2004 19:06:00 -0000 [thread overview]
Message-ID: <417565AA.7050307@gnu.org> (raw)
In-Reply-To: <41755D36.3090102@gnu.org>
[-- 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
prev parent reply other threads:[~2004-10-19 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 18:30 Andrew Cagney
2004-10-19 19:06 ` Andrew Cagney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=417565AA.7050307@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox