From: Daniel Berlin <dberlin@dberlin.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: To all GDB committers
Date: Tue, 28 Feb 2006 16:30:00 -0000 [thread overview]
Message-ID: <1141139128.9157.121.camel@localhost> (raw)
In-Reply-To: <20060227201508.GA1345@adacore.com>
On Mon, 2006-02-27 at 12:15 -0800, Joel Brobecker wrote:
> Hello everyone,
>
> Since we now have patch champions, a couple of us are tracking the
> patches sent to the GDB mailing list, and try to make sure that none
> of them fall through the cracks.
>
> To help us in our job, would you mind always sending a confirmation
> that a given patch has been committed, please? In particular, it would
> be very helpful for patches that you send saying that you "will commit
> in a few days pending objections".
>
> Thanks a lot,
Joel, if it would be useful to you or the gdb folks, i'm happy to
attempt to set up a patch queue for gdb like the one we have for gcc:
http://www.dberlin.org/patches/
next prev parent reply other threads:[~2006-02-28 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 20:36 Joel Brobecker
2006-02-28 16:30 ` Daniel Berlin [this message]
2006-03-02 1:32 ` Joel Brobecker
2006-03-02 2:08 ` Daniel Berlin
2006-03-02 10:44 ` Andrew STUBBS
2006-03-03 11:23 ` Wu Zhou
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=1141139128.9157.121.camel@localhost \
--to=dberlin@dberlin.org \
--cc=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