From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: What is on the 5.1 branch; Was: [rfc] Re: read_register_bytes() bug; was my Regcache revamp
Date: Tue, 21 Aug 2001 06:53:00 -0000 [thread overview]
Message-ID: <3B80A35B.3060504@cygnus.com> (raw)
In-Reply-To: <9743-Sun19Aug2001093055+0300-eliz@is.elta.co.il>
> Frankly, for quite some time I'm confused by the RFC's and RFA's
> posted here. Are they all meant to go to the branch as well as the
> trunk? If so, is it wise to make such changes after cutting the
> release branch?
As far as I know most of the patches going past at the moment are not
going onto the branch(1). Hmm, quick check, I've attached a copy of the
5.1 ChangeLog.
This current thread/patch, however is interesting, I was not thinking of
it as something for the 5.1 branch, but, yes, it probably is.
> Perhaps in the future each patch could tell explicitly whether it is
> meant ffor the branch or not, to prevent confusion.
I've been using the prefix [.../5.1] for anything 5.1 related.
enjoy, (I hope this helps)
Andrew
Now to try to get http://sources.redhat.com/gdb/ ==
http://www.gnu.org/software/gdb/ .
(1) For me it is stuff like overhalling the floating-point code; fixing
some nasty true multi-arch initialization problems; more MI and LIBGDB
cleanup; more multi-arch; ...
next prev parent reply other threads:[~2001-08-21 6:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-18 11:08 Andrew Cagney
2001-08-18 14:04 ` [rfc] " Andrew Cagney
[not found] ` <9743-Sun19Aug2001093055+0300-eliz@is.elta.co.il>
2001-08-21 6:53 ` Andrew Cagney [this message]
2001-08-19 23:10 ` What is on the 5.1 branch; Was: " Eli Zaretskii
2001-08-19 23:16 ` Daniel Jacobowitz
2001-08-20 2:09 ` Eli Zaretskii
2001-08-20 15:07 ` Mark Kettenis
2001-08-20 23:43 ` Eli Zaretskii
2001-08-21 8:17 ` Andrew Cagney
2001-08-21 9:23 ` Eli Zaretskii
2001-08-21 6:52 ` Andrew Cagney
2001-08-21 6:52 ` Kevin Buettner
2001-08-21 6:53 ` Andrew Cagney
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=3B80A35B.3060504@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--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