From 90ab7e9a68d5b4eef2d2d4afa384a458d775cce3 Mon Sep 17 00:00:00 2001 From: Nick Clifton Date: Wed, 11 Jul 2001 09:06:49 +0000 Subject: [PATCH] Add notes about branch checkins --- binutils/ChangeLog | 4 ++++ binutils/MAINTAINERS | 12 ++++++++++++ 2 files changed, 16 insertions(+) diff --git a/binutils/ChangeLog b/binutils/ChangeLog index 5249dabfc6f..4a7c4f79bc6 100644 --- a/binutils/ChangeLog +++ b/binutils/ChangeLog @@ -1,3 +1,7 @@ +2001-07-11 Nick Clifton + + * MAINTAINERS: Add notes about branch checkins. + 2001-07-05 Daniel Berlin * readelf.c (display_debug_macinfo): New function, display diff --git a/binutils/MAINTAINERS b/binutils/MAINTAINERS index 9220c735b44..4c50bd5c7cf 100644 --- a/binutils/MAINTAINERS +++ b/binutils/MAINTAINERS @@ -91,3 +91,15 @@ spelling mistakes, blatantly incorrect code (where the correct code is also blatantly obvious), and so on. Obvious fixes should always be small, the larger they are, the more likely it is that they contain some un-obvious side effect or consequence. + + --------- 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 maintaining 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 -- 2.30.2