All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Giacomo A. Catenazzi" <cate@cateee.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.24
Date: Fri, 25 Jan 2008 10:10:11 +0100	[thread overview]
Message-ID: <4799A773.2030702@cateee.net> (raw)
In-Reply-To: <alpine.LFD.1.00.0801241529440.15329@hp.linux-foundation.org>

Linus Torvalds wrote:
> 
> On Thu, 24 Jan 2008, Linus Torvalds wrote:
>> The release is out there (both git trees and as tarballs/patches), and for 
>> the next week many kernel developers will be at (or flying into/out of) 
>> LCA in Melbourne, so let's hope it's a good one.
> 
> Since I already had two kernel developers asking about the merge window 
> and whether people (including me) traveling will impact it, the plan right 
> now is to keep the impact pretty minimal. So yes, it will probably extend 
> the window from the regular two weeks, but *hopefully* not by more than a 
> few days.

As a tester, I'm not so happy.
The last few merge windows were a nightmare for us (the tester).
It remember me the 2.1.x times, but with few differences:
- more changes, so bugs are unnoticed/ignored in the first weeks or
- or people are pushing more patches possible, so they delay
   bug corrections to later times (after merge windows).

If it continues so, I should stop testing the kernel on the
merge windows (but it seems that other testers already give up
the early merge phase).

As a tester I would like:
- slow merges, so that developer could rebase and test
   (compile test) the interaction of the new code.
- you will introduce a new step on git management:
   Every changeset is compile-tested before going out to the world.
   I think this can be done automatically, and I think that one or
   two configurations are enough to find most of the problems.

Happy LCA,
ciao
	cate

  reply	other threads:[~2008-01-25  9:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 23:17 Linux 2.6.24 Linus Torvalds
2008-01-24 23:41 ` Linus Torvalds
2008-01-25  9:10   ` Giacomo A. Catenazzi [this message]
2008-01-25  9:58     ` Valdis.Kletnieks
2008-01-25 11:58       ` Rafael J. Wysocki
2008-01-25 12:34         ` Giacomo A. Catenazzi
2008-01-25 23:50           ` Stefan Richter
2008-01-26  0:42             ` using LKML for subsystem development (was Re: Linux 2.6.24) Stefan Richter
2008-01-26  3:28               ` Valdis.Kletnieks
2008-01-26 13:31                 ` using LKML for subsystem development Stefan Richter
2008-01-27  7:37                   ` Valdis.Kletnieks
2008-01-26 11:28               ` using LKML for subsystem development (was Re: Linux 2.6.24) Ingo Molnar
2008-01-26 14:07                 ` using LKML for subsystem development David Miller
2008-01-26 14:45                   ` Stefan Richter
2008-01-26 14:25                 ` Stefan Richter
2008-02-01  9:40                   ` Ingo Molnar
2008-02-01 19:53                     ` Stefan Richter
2008-01-26  3:19             ` Linux 2.6.24 Valdis.Kletnieks
2008-01-25 11:35     ` Ingo Molnar
2008-01-25 10:11 ` [PATCH] linux-2.6.24/drivers/hid/hid-input.c Philipp Matthias Hahn
2008-01-25 10:30   ` Jiri Kosina
2008-02-03 12:35 ` Linux 2.6.24 Jan Engelhardt

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=4799A773.2030702@cateee.net \
    --to=cate@cateee.net \
    --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 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.