From 36c2118fc9c46395d758d50cb36d4469d2081a38 Mon Sep 17 00:00:00 2001 From: Andrew Cagney Date: Fri, 10 Mar 2000 00:52:40 +0000 Subject: [PATCH] Devolve area maintaineship responsibilities. --- gdb/ChangeLog | 4 ++++ gdb/MAINTAINERS | 14 ++++++-------- 2 files changed, 10 insertions(+), 8 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 5517bc1a117..a8b580a0605 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +Fri Mar 10 11:44:55 2000 Andrew Cagney + + * MAINTAINERS: Devolve responsibility for domain maintenance. + 2000-03-06 Elena Zannoni * minsyms.c (prim_record_minimal_symbol_and_info): Add comment. diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS index 4d741d25e0a..47e594dc67a 100644 --- a/gdb/MAINTAINERS +++ b/gdb/MAINTAINERS @@ -14,14 +14,12 @@ Peter Schauer Peter.Schauer@regent.e-technik.tu-muenchen.de Note individuals who maintain parts of the debugger need approval to check in changes outside of the immediate domain that they maintain. -If there is no maintainer for a given domain then the problem falls to -the head maintainer. - -If there are several maintainers for a given domain then the problem -falls to the first maintainer. The second and third maintainers are -firstly known to have expertise in the given domain and secondly are -available to step in if the first maintainer is to be absent for any -reason. +If there is no maintainer for a given domain then the responsibility +falls to the head maintainer. + +If there are several maintainers for a given domain then +responsibility falls to the first maintainer. The first maintainer is +free to devolve that responsibility among the other maintainers. Target/Architecture: -- 2.30.2