From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Patch tracker now available
Date: Fri, 09 Jun 2006 17:00:00 -0000 [thread overview]
Message-ID: <20060609142816.GA28863@nevyn.them.org> (raw)
In-Reply-To: <20060330001459.GA13813@nevyn.them.org>
On Wed, Mar 29, 2006 at 07:14:59PM -0500, Daniel Jacobowitz wrote:
> Daniel Berlin offered in February to set up a patch queue. It's some
> custom software that he wrote for GCC, after two consecutive GCC Summits
> in which people agreed that they wanted some automated way to keep track of
> patches, but no one came up with anything that seemed usable.
Everyone who responded liked this idea, so I've set one up. It was a
pile of work to get running, so I hope it's useful :-)
It's here:
http://gdb.false.org/patches
It is certainly not mandatory for patch submitters or reviewers. It
has both an email interface (it scans the web archives hourly looking
for commands) and a web interface; if I find it useful I can add
patches to it even when they weren't posted with appropriate tags.
There's some instructions on how to use it by email up top of the list.
If you have any suggestions or problems, please let me know.
If it proves useful, we can make it more prominent, for instance by a
link from the GDB web site. In the mean time, I encourage patch
submitters to use it.
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.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-09 14:28 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 ` Daniel Jacobowitz [this message]
2006-06-09 17:56 ` Patch tracker now available 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=20060609142816.GA28863@nevyn.them.org \
--to=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