From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sources.redhat.com
Subject: [MAINTAINERS] Removing self from patch champions
Date: Fri, 10 Mar 2006 11:18:00 -0000 [thread overview]
Message-ID: <20060310021109.GO1009@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
Hello all,
Sadly, I would like to step down from my Patch Champion position
because my current workload prevents me from reading the gdb-patches
mailing-list sometimes 10 days at a time. Hardly appropriate for
tracking patches, and also work on coding style, FSF assignments,
etc. I'd rather spend my occasional free time doing some cleanups
or other development tasks that are not directly related to my
AdaCore work.
This leaves Daniel as the only patch champion. I think at least
one more volunteer would be greatly appreciated. The beauty of
this position is that it doesn't require a good knowledge of the
debugger code...
Note that in practice, I have found the maintainers to be VERY
responsive lately. Not much the patch champions could do but
watch the maintainers do an awsome job. Congrats guys, and thanks!
I have committed the following update:
2006-03-09 Joel Brobecker <brobecker@adacore.com>
* MAINTAINERS (Patch Champions): Remove self.
Thanks,
--
Joel
[-- Attachment #2: MAINT.diff --]
[-- Type: text/plain, Size: 475 bytes --]
Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/gdb/MAINTAINERS,v
retrieving revision 1.338
diff -u -p -r1.338 MAINTAINERS
--- MAINTAINERS 7 Feb 2006 15:42:54 -0000 1.338
+++ MAINTAINERS 10 Mar 2006 02:01:27 -0000
@@ -192,7 +192,6 @@ patches; and ensure that contributors ar
Current patch champions (in alphabetical order):
- Joel Brobecker <brobecker@adacore.com>
Daniel Jacobowitz <dan@debian.org>
next reply other threads:[~2006-03-10 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 11:18 Joel Brobecker [this message]
2006-03-25 7:01 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060310021109.GO1009@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox