From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Patch tracker now available
Date: Sat, 10 Jun 2006 01:09:00 -0000 [thread overview]
Message-ID: <17546.4915.211704.209128@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20060609142816.GA28863@nevyn.them.org>
> There is an associated rant, which is that I'd really appreciate more
> help in reviewing submitted patches. I hope that adding tracking will
> make it easier to see what needs review.
On that note, at some stage I would like to volunteer as MI maintainer. This
is really just a statement of intent, as I would like to wait till after the
release of Emacs 22. If my changes are well received then I think I would be
in a good position, as I would hopefully be getting feedback from the user
community.
To clarify, I would be prepared to review patches on the MI interface itself,
and do not pretend that I could currently cover the parts which delve deep into
the internals of GDB, as Andrew (or Elena) would possibly have done.
Oh yes, about your patch tracker. I might have inadvertantly deleted a patch.
I didn't realise it would be so easy, maybe a confirmation would be a good
idea. Perhaps I've disqualified myself already ...oops, sorry!
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-06-10 0:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 1:14 Using a patch queue? Daniel Jacobowitz
2006-03-30 1:27 ` Jim Blandy
2006-03-30 7:10 ` Bob Rossi
2006-03-30 10:03 ` Ramana Radhakrishnan
2006-06-09 17:00 ` Patch tracker now available Daniel Jacobowitz
2006-06-09 17:56 ` PAUL GILLIAM
2006-06-10 1:09 ` Nick Roberts [this message]
2006-06-10 16:04 ` Daniel Jacobowitz
2006-06-23 21:52 ` 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=17546.4915.211704.209128@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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