From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: A modest proposal -- We need a patch tracking system.
Date: 30 Jan 2002 21:36:05 -0800 [thread overview]
Message-ID: <a3al45$1fs$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0201290902100.32617-100000@imladris.surriel.com> <200201291156.g0TBudE28106@Port.imtp.ilyichevsk.odessa.ua> <3C573428.3000404@fit.edu>
Followup to: <3C573428.3000404@fit.edu>
By author: Kervin Pierre <kpierre@fit.edu>
In newsgroup: linux.dev.kernel
>
> Public patch tracking system/queue, maybe something derived from bugzilla.
>
> (i) patches are sent to the maintainer and entered into the system.
>
> (ii) reviewed patches are update appropriately, eg. ( "reject - untidy,
> please fix", "accept - expected version 2.4.18pre19" etc. )
>
> (iii) patch versions, updates can be kept, as in mozilla's bugzilla
> site. And comments on that patch can also be kept right along side the
> code.
>
> Regardless of wether the current system is changed or not, the linux
> kernel would benefit from a central, searchable, public repository of
> patches.
>
> The code is available, bugzilla has all this functionality today.
>
> So here's hoping for a patchzilla.kernel.org :)
>
If Linus et al signs on to the idea, I'm sure we can build it...
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-01-31 5:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 1:53 A modest proposal -- We need a patch penguin John Weber
2002-01-29 5:15 ` Rob Landley
2002-01-29 11:04 ` Rik van Riel
2002-01-29 15:56 ` Denis Vlasenko
2002-01-29 23:45 ` A modest proposal -- We need a patch tracking system Kervin Pierre
2002-01-31 5:36 ` H. Peter Anvin [this message]
2002-01-29 18:14 ` A modest proposal -- We need a patch penguin Horst von Brand
2002-01-29 18:33 ` Olaf Dietsche
2002-01-29 22:12 ` James Stevenson
2002-01-30 1:00 ` Stuart Young
2002-01-30 1:18 ` Jeff Garzik
2002-01-30 1:41 ` Daniel Phillips
2002-01-30 1:32 ` Stuart Young
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='a3al45$1fs$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.