[PATCH RFA] two MIPS opcodes patches to pull up to branch?

[PATCH RFA] two MIPS opcodes patches to pull up to branch?

[cgd]

I'd like to get the following patches approved for the 5.2 branch:

http://sources.redhat.com/ml/binutils/2002-03/msg00136.html

[opcodes/ChangeLog]
2002-03-06  Chris Demetriou  <cgd@broadcom.com>

        * mips-opc.c (mips_builtin_opcodes): Mark "pref" as being
        present on I4.

        * mips-opc.c (mips_builtin_opcodes): Add "movn.ps" and
          "movz.ps".

and

http://sources.redhat.com/ml/binutils/2002-03/msg00202.html

[ opcodes/ChangeLog ]
2002-03-11  Chris Demetriou  <cgd@broadcom.com>

        * mips-dis.c (is_newabi): Fix ABI decoding.


Both have been approved and applied to mainline binutils, and they
both seem to apply to the gdb 5.2 branch.


chris

Re: [PATCH RFA] two MIPS opcodes patches to pull up to branch?

[Andrew Cagney]

Yep, fine.  What's the worst that could happen, the mips breaks? :-)

Andrew

> I'd like to get the following patches approved for the 5.2 branch:
> 
> http://sources.redhat.com/ml/binutils/2002-03/msg00136.html
> 
> [opcodes/ChangeLog]
> 2002-03-06  Chris Demetriou  <cgd@broadcom.com>
> 
> * mips-opc.c (mips_builtin_opcodes): Mark "pref" as being
>         present on I4.
> 
>         * mips-opc.c (mips_builtin_opcodes): Add "movn.ps" and
>           "movz.ps".
> 
> and
> 
> http://sources.redhat.com/ml/binutils/2002-03/msg00202.html
> 
> [ opcodes/ChangeLog ]
> 2002-03-11  Chris Demetriou  <cgd@broadcom.com>
> 
> * mips-dis.c (is_newabi): Fix ABI decoding.
> 
> 
> Both have been approved and applied to mainline binutils, and they
> both seem to apply to the gdb 5.2 branch.

Re: [PATCH RFA] two MIPS opcodes patches to pull up to branch?

[cgd]

At Sun, 17 Mar 2002 01:49:40 +0000 (UTC), "Andrew Cagney" wrote:
> Yep, fine.  What's the worst that could happen, the mips breaks? :-)

What's the format to be used for branch ChangeLogs?

change log as originally committed (i.e., using original commit date)?
new entry at top of file or sorted in by original date?  etc.

I didn't see anything about this in your recently posted branch
policy...


thanks,

chris

Re: [PATCH RFA] two MIPS opcodes patches to pull up to branch?

[Eli Zaretskii]

On 24 Mar 2002 cgd@broadcom.com wrote:

> What's the format to be used for branch ChangeLogs?
> 
> change log as originally committed (i.e., using original commit date)?
> new entry at top of file or sorted in by original date?  etc.

For changes on the branch, you are supposed to modify the ChangeLog
files from the branch only.  The date should be the date of the commit 
(otherwise, the logs are not in chronological order, which makes it hard 
to track change history).

In other words, you should do the same as you do on the trunk.  That's 
why there's no mention of anything special in the branch policy text.

Re: [PATCH RFA] two MIPS opcodes patches to pull up to branch?

[Andrew Cagney]

> On 24 Mar 2002 cgd@broadcom.com wrote:
> 
> 
>> What's the format to be used for branch ChangeLogs?
>> 
>> change log as originally committed (i.e., using original commit date)?
>> new entry at top of file or sorted in by original date?  etc.
> 
> 
> For changes on the branch, you are supposed to modify the ChangeLog
> files from the branch only.  The date should be the date of the commit 
> (otherwise, the logs are not in chronological order, which makes it hard 
> to track change history).

Yep

> In other words, you should do the same as you do on the trunk.  That's 
> why there's no mention of anything special in the branch policy text.

If the dates will differ, it doesn't hurt to add a ``From <date> <who>'' 
or ``Import <date> <who>'' or ...

enjoy,
Andrew