mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Jan Engelhardt" <jengelh@computergmbh.de>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	davem@davemloft.net, "Andrew Morton" <akpm@linux-foundation.org>
Subject: New branch for +1 kernel Was:Re: [PATCH] Use __u64 in aligned_u64's definition
Date: Thu, 3 Jan 2008 02:11:44 +0330	[thread overview]
Message-ID: <4d8e3fd30801021441h51f180des465f94ed24b107c2@mail.gmail.com> (raw)

On 1/3/08, Linus Torvalds <torvalds@linux-foundation.org> wrote:

> > 2.6.25 actually. You don't take patches this early, do you?
>
> Yeah, no, I don't take patches early. I've considered setting up another
> branch for early patches, but decided that I'm (a) lazy and (b) better off
> encouraging people in the late -rc timeframe to just concentrate on the
> -rc's, not the next version.


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.?
Sounds like a good way to be more strict about regressions and
incentive people to solve regressions quicker.

Ciao,
-- 
Paolo
http://paolo.ciarrocchi.googlepages.com/

             reply	other threads:[~2008-01-02 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 22:41 Paolo Ciarrocchi [this message]
2008-01-03 16:00 ` Stefan Richter
2008-01-03 16:17   ` Paolo Ciarrocchi

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=4d8e3fd30801021441h51f180des465f94ed24b107c2@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=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®