From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: "Stefan Richter" <stefanr@s5r6.in-berlin.de>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Jan Engelhardt" <jengelh@computergmbh.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
davem@davemloft.net, "Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: New branch for +1 kernel Was:Re: [PATCH] Use __u64 in aligned_u64's definition
Date: Thu, 3 Jan 2008 19:47:59 +0330 [thread overview]
Message-ID: <4d8e3fd30801030817t7c468c66id5740ae06ae8a254@mail.gmail.com> (raw)
In-Reply-To: <477D0694.1010005@s5r6.in-berlin.de>
On 1/3/08, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> Paolo Ciarrocchi wrote:
> > This is something i was thinking to suggest.
> > Kernel is made of a lot of different "areas" and the regression list
> > is a great tool for monitoring every single area so why not opening a
> > new branch and accepting patches only for areas which are not in the
> > current regression list.?
>
> Some regressions can't be easily associated with an "area". And when
> they can, consider the overhead involved with frequently kicking out
> patchsets and taking them in again, based on when regressions become
> known and when they are fixed, respectively.
>
> > Sounds like a good way to be more strict about regressions and
> > incentive people to solve regressions quicker.
>
> To create such a motivation, that branch or tree would have to have a
> practical use in development. So what purpose would such a tree
> fulfill, considering that we already have a myriad of topic trees and
> the -mm tree for testing and preintegration?
That branch/tree would relax i bit the rule of "two weeks for merging
new stuff" for people who proven to have merged good quality code.
Ciao,
--
Paolo
http://paolo.ciarrocchi.googlepages.com/
prev parent reply other threads:[~2008-01-03 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 22:41 Paolo Ciarrocchi
2008-01-03 16:00 ` Stefan Richter
2008-01-03 16:17 ` Paolo Ciarrocchi [this message]
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=4d8e3fd30801030817t7c468c66id5740ae06ae8a254@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®