From: "Jim Blandy" <jimb@red-bean.com>
To: gdb@sourceware.org
Subject: Re: Using a patch queue?
Date: Thu, 30 Mar 2006 01:27:00 -0000 [thread overview]
Message-ID: <8f2776cb0603291631i5da68410if3a1ead1bdac3f80@mail.gmail.com> (raw)
In-Reply-To: <20060330001459.GA13813@nevyn.them.org>
On 3/29/06, Daniel Jacobowitz <drow@false.org> wrote:
> I wouldn't mind having a better tool than my inbox to track down what needs
> looking at; I don't have enough time to review everything that needs
> reviewing as it is. Anyone else have an opinion?
I'd been thinking of something along those lines for a while. It
seems really easy to set up, and participation is voluntary, so we
should give it a try.
next prev parent reply other threads:[~2006-03-30 0:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 1:14 Daniel Jacobowitz
2006-03-30 1:27 ` Jim Blandy [this message]
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
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=8f2776cb0603291631i5da68410if3a1ead1bdac3f80@mail.gmail.com \
--to=jimb@red-bean.com \
--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