2.12_branch commit rules (current release branch rules revisited)

["David O'Brien" <obrien at FreeBSD dot org>]

Phil agreed to this (Message-Id:
<E15JxDY-0002Ft-00@kings-cross.london.uk.eu.org>).  Is this now off the
table?

----- Forwarded message from Nick Clifton <nickc@cambridge.redhat.com> -----

From: Nick Clifton <nickc@cambridge.redhat.com>
Subject: Re: [PATCH] basename buffer gets spammed in `ld'
Date: 10 Jul 2001 11:40:22 +0100
To: DJ Delorie <dj@delorie.com>, philb@gnu.org
Cc: binutils@sourceware.cygnus.com
Mailing-List: contact binutils-help@sourceware.cygnus.com; run by ezmlm
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7

Hi DJ,

> Nick - can we add a "current branches and checkin rules" section on
> the binutils web page?

A good idea.  How about something like this:

	       --------- Branch Checkins ---------

    If a patch is approved for check in to the mainline sources,
    it can also be checked into the current release branch.
    Normally however only bug fixes should be applied to the branch.
    New features, new ports, etc, should be restricted to the
    mainline.  (Otherwise the burden of maintaing the branch in
    sync with the mainline becomes too great).  If you are
    uncertain as to whether a patch is appropriate for the branch,
    ask the branch maintainer.  This is:

        Philip Blundell  <philb@gnu.org>

Phil, do you agree ?  Would you prefer to have patches always
submiited for your approval before they are applied to the branch ?

Cheers
        Nick
----- End forwarded message -----