Re: FYI: gdbserver branch merges

[Andrew Cagney <ac131313@cygnus.com>]

> On Fri, Mar 29, 2002 at 08:31:57PM +0100, Andreas Jaeger wrote:
> 
>> Daniel Jacobowitz <drow@mvista.com> writes:
>> 
> 
>> > I've moved these patches to the branch.  This is all the gdbserver
>> > changes except for x86-64 (which was too invasive, and I don't consider
>> > urgent since x86-64 is not yet a production architecture) since we
>> > branched.  For the signals code I created new files without removing
>> > the old definitions.
> 
>> 
>> For when is 5.2 planned and when is the next release?  Since x86-64 is
> 
> 
> I don't know what the current plan is, but it should be within the next
> two/three weeks if all goes well.

Yes.  The only thing I'm still trying to resolve is the HP/UX cc -Ae 
patches.  There are some symtab bugs but I'm not going to try to resolve 
them.

That suggests:
	this weekend - snap (2002-04-06)
	next weekend - snap (2002-04-13)
	saturday fortnight - release (2002-04-20)

>> currently not production ready, we can make big changes.  The first
>> hammer systems are going to ship by the end of the year so that I
>> expect that we'll use GDB 5.2 on them.  Could you rethink this,
>> please?
> 
> 
> There should be another release by then; I think Andrew was hoping for
> one mid-April and one in late September.  If you'd prefer to have the
> x86-64 changes on the branch you're welcome to merge them; I was just
> doing the bits I was confident in, and the x86-64 changes were too
> large for someone who doesn't know anything about the port to merge
> safely.  The gdbserver bits also need to bring in all the recent
> changes to the tdep files.

I believe the most recent x86-64 changes have already been pulled into 
the branch (well at least the non-gdbserver bits).

Releases are trying to be ~4 months: Mar-Apr, Jul-Aug and Nov-Dec time 
frames.  (The cron job that tracks the schedule indicates 2002-07-07 so 
I think it is broken).

enjoy,
Andrew