4.3 target deprecation patch part 1: c4x removal, whole-target deprecations

Pompapathi V Gadad Pompapathi.V.Gadad@nsc.com
Fri Feb 29 13:25:00 GMT 2008


Hello Joseph S. Myers,
Thanks for reply. My individual assignment process with the FSF is 
complete. I have submitted patches for another target CR16 and it has 
been reviewed. However, it has not be committed to trunk yet.

OK. We will make necessary changes in the patches to include the removal 
of deprecation and post the results as soon as possible.

Thanks a lot,
Pompa

Joseph S. Myers wrote:
> The question of maintainership will need to be decided by the Steering 
> Committee, but before you can become the maintainer you should have 
> established a record of submitting good patches to the port that conform 
> to the GNU Coding Standards etc.; depending on the status of any corporate 
> assignment, you may also need to have personal copyright assignment papers 
> on file at the FSF.
>
> When you have patches to the port ready that make any changes necessary to 
> get it in good working order, you can include the change to config.gcc to 
> remove the deprecation along with those patches, and post the test results 
> for the patched compiler to gcc-testresults (indicating in the test 
> results posting what patches are applied).  If any changes required are 
> confined to the crx port or otherwise clearly safe for other targets, you 
> may also be able to remove the deprecation on 4.3 branch.
>
> You should plan on getting the patches in - including doing any necessary 
> paperwork and pinging patches needing review as necessary - within the 
> next couple of months; deprecated ports are likely to be removed at that 
> point unless they have seen sufficient activity to revive them.
>
>   




More information about the Gcc mailing list