From: Kervin Pierre <kpierre@fit.edu>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: linux-kernel@vger.kernel.org
Subject: Re: A modest proposal -- We need a patch tracking system.
Date: Tue, 29 Jan 2002 18:45:44 -0500 [thread overview]
Message-ID: <3C573428.3000404@fit.edu> (raw)
In-Reply-To: <Pine.LNX.4.33L.0201290902100.32617-100000@imladris.surriel.com> <200201291156.g0TBudE28106@Port.imtp.ilyichevsk.odessa.ua>
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 :)
--Kervin
Denis Vlasenko wrote:
> On 29 January 2002 09:04, Rik van Riel wrote:
>
>>On Mon, 28 Jan 2002, John Weber wrote:
>>
>>>I would be happy to serve as patch penguin, as I plan on collecting all
>>>patches anyway in my new duties as maintainer of www.linuxhq.com.
>>>
>>>we have the hardware/network capacity to serve as a limitless queue of
>>>waiting patches for Linus.
>>>
>>Please don't just accumulate stuff.
>>
>
> Right. Accepting any patch is wrong policy. You'll be swamped.
> Patch must be marked "applies to 2.N.M", patch tracking system must check
> that automagically.
>
> Also each patch(set) can be commented by general public and by maintainers.
> If there is _no_ comment from any of _maintainers_ (i.e. it is not reviewed
> or found too ugly to worth commenting) it is automatically dropped from the
> system after some time. This will force patch authors to care about code
> quality.
>
> If patch is too old (several releases behind) system can mail author(s):
> "Warning. Your patchset #3476346 needs rediffing. It will be dropped
> otherwise"
>
> These "small" details determine whether system is useful or just turns into
> huge pile of patches of questionable value.
> --
> vda
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
--
http://linuxquestions.org/ - Ask linux questions, give linux help.
next prev parent reply other threads:[~2002-01-29 23:41 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 ` Kervin Pierre [this message]
2002-01-31 5:36 ` A modest proposal -- We need a patch tracking system H. Peter Anvin
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=3C573428.3000404@fit.edu \
--to=kpierre@fit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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