Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>
Cc: Joel Brobecker <brobecker@gnat.com>, gdb@sources.redhat.com
Subject: Re: GDB 6.1.1 2004-05-21-gmt
Date: Wed, 26 May 2004 17:15:00 -0000	[thread overview]
Message-ID: <40B4D0A9.7080104@gnu.org> (raw)
In-Reply-To: <20040525222803.GQ7207@tausq.org>

>>There seem to be a significant number of fixes even without this - 
>>> basics such as value return and backtraces.
>>> 
>>> As for the arch and other core changes, they can wait until 6.2.
> 
> 
> ok... it's just that the gdbarch change will fix MANY problems in the
> testsuite. :)
> 
> what is the process for getting patches into 6.1? Are they resubmitted
> one-by-one, or do i do a wholesale diff of hppa-specific files? There
> are about 30 patches from me that has gone into CVS since 6.1.

Something like:

$ cp src/gdb/hppa*.[hc] 61/src/gdb ; emacs 61/src/gdb/ChangeLog

For the changelog suggest both mentioning that the stuff is an import 
from the mainline and list a concat of the original changelogs (minus 
dates et.al.).

Most important though is:

$ emacs 61/src/gdb/NEWS 61/src/gdb/ChangeLog

where there should be a brief of how the update affects (benefits) the 
user - mention a few key bug fixes for instance.

When it comes to architecture specific changes GDB is very liberal - the 
worst they can do is break that architecture and presumably the person 
pulling in the changes is testing it :-)

enjoy,
Andrew

PS: I've some incompatible frame changes on hold waiting for 6.1.1 to 
ship - help make these imports easier.



  reply	other threads:[~2004-05-26 17:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25 21:22 Andrew Cagney
2004-05-25 21:36 ` Randolph Chung
2004-05-25 21:47 ` Joel Brobecker
2004-05-25 21:53   ` Randolph Chung
2004-05-25 22:22     ` Andrew Cagney
2004-05-25 22:28       ` Randolph Chung
2004-05-26 17:15         ` Andrew Cagney [this message]
2004-05-26 18:10           ` Randolph Chung
2004-05-26 22:13         ` Manoj Iyer
2004-05-27 20:19           ` Andrew Cagney
2004-05-26 17:58 ` Andrew Cagney
2004-06-07 18:18 ` GDB 6.1.1 2004-05-21-gmt [not] Andrew Cagney
2004-05-26  0:08 GDB 6.1.1 2004-05-21-gmt Michael Elizabeth Chastain
2004-05-27 10:54 Michael Elizabeth Chastain

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=40B4D0A9.7080104@gnu.org \
    --to=cagney@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=gdb@sources.redhat.com \
    --cc=randolph@tausq.org \
    /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