Re: GDB 6 schedule

["Jafa" <jafa@silicondust.com>]

Hi Andrew,

The port consists of a tdep file and a remote back-end over two files (there
is a lot of code in the remote back-end and two clear levels of
abstraction).

The trunk has moved on considerably sinse the last major release and I need
some of the new features such as reg groups (several hundred registers).

If there is a concern then I would be happy if a tempory branch of the gdb
directory was created to work on for the next few weeks prior to merging to
the trunk, however as you say, the worst that can happen is that the ip2k
port doesn't work.

I would appreciate your help and time to make this work.

Thanks

Nick

----- Original Message -----
From: "Andrew Cagney" <ac131313@redhat.com>
To: <jafa@silicondust.com>
Sent: Friday, May 16, 2003 8:27 PM
Subject: Re: GDB 6 schedule


*This message was transferred with a trial version of CommuniGate(tm) Pro*
> Hi Andrew,
>
> I have been meaning to re-sync with the trunk and get the ip2k port
> submitted but got distracted.
>
> Any chance we can work to get the ip2k port submitted in time? (I am not
> sure what the general policy is for a quite tiem before the branch)

In the past new architectures have been added to a release branch.  In
all cases though, the change was contained to single -tdep.c file (the
worst it could do was not work).

However, the changes first need to be approved for the mainline.

Andrew



> ----- Original Message -----
> From: "Andrew Cagney" <ac131313@redhat.com>
> To: <jafa@silicondust.com>
> Sent: Friday, May 16, 2003 5:57 PM
> Subject: GDB 6 schedule
>
>
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> Here is a vague GDB 6 schedule:
>
> 17-05-2003 - today
> 14-06-2003 - branch
> 26-07-2003 - release
>
> That's 4 weeks to branch, and a further 6 weeks to release ....
>
> Andrew
>
>
>
>