aboutsummaryrefslogtreecommitdiff
path: root/binutils/MAINTAINERS
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2001-07-11 09:06:49 +0000
committerNick Clifton <nickc@redhat.com>2001-07-11 09:06:49 +0000
commit90ab7e9a68d5b4eef2d2d4afa384a458d775cce3 (patch)
tree47949dc4f73c7a42e98cb6199a29a00ff7ddb716 /binutils/MAINTAINERS
parentccb945b81ed53beb1b3849800949c409b4585140 (diff)
downloadgdb-90ab7e9a68d5b4eef2d2d4afa384a458d775cce3.zip
gdb-90ab7e9a68d5b4eef2d2d4afa384a458d775cce3.tar.gz
gdb-90ab7e9a68d5b4eef2d2d4afa384a458d775cce3.tar.bz2
Add notes about branch checkins
Diffstat (limited to 'binutils/MAINTAINERS')
-rw-r--r--binutils/MAINTAINERS12
1 files changed, 12 insertions, 0 deletions
diff --git a/binutils/MAINTAINERS b/binutils/MAINTAINERS
index 9220c73..4c50bd5 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 <philb@gnu.org>