Branch creation policy?

[Mark Mitchell <mark at codesourcery dot com>]

Is there any objection to creating newlib branches under the same
policies that have been established for Binutils and GDB?

>From the Binutils MAINTAINERS file:

> Anyone with at least write-after-approval access may create a branch
> to use for their own development purposes.  In keeping with FSF
> policies, all patches applied to such a branch must come from people
> with appropriate copyright assignments on file.  All legal
> requirements that would apply to any other contribution apply equally
> to contributions on a branch.
> 
> Before creating the branch, you should select a name for the branch of
> the form:
> 
>   binutils-<org>-<name>
> 
> where "org" is the initials of your organization, or your own initials
> if you are acting as an individual.  For example, for a branch created
> by The GNUDist Company, "tgc" would be an appropriate choice for
> "org".  It's up to each organization to select an appropriate choice
> for "name"; some organizations may use more structure than others, so
> "name" may contain additional hyphens.
> 
> Suppose that The GNUDist Company was creating a branch to develop a
> port of Binutils to the FullMonty processor.  Then, an appropriate
> choice of branch name would be:
> 
>   binutils-tgc-fm

There is then some technical information below that point.

Thanks,

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713