[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[OT] dealing with those impatient people (was Re: Re: 2.4.13 Stability?)

Just thinking...

Maybe... procmail (regex) + perl (regex) + list of newest kernels =
automagic script to tell people to be a little understanding (and not
waste emails on asking "when will an ext3 patch against y's z.z.zz
kernel tree be out?")... ;-)) Heheh...

I think we can't appreciate the work of the ext3 developers enough!

On Friday, 26 October, 2001, Craig Dickson scribbled:
> It might help to have a policy statement on the ext3-2.4 web page saying
> something like "Don't expect patches for a new kernel until it's been
> out a few days." Though, of course, then you'll get people who read that
> as a promise that a patch _will_ be available after only a few days,
> which may not always be the case. There never were patches for 2.4.11 or
> 2.4.12, presumably because both releases were short-lived and
> problematic.
> I'm not sure how one could say it and get the idea across properly.
> Ideally, it should be a single, simple, unchanging policy statement so
> the ext3 team doesn't have to redo it every time a new kernel comes out.
> I suppose one could risk being perceived as rude, and just say, "Patches
> will be released when they're ready -- don't bug us about it." Which
> would be fine with me, actually. I'm happy to wait until the ext3 team
> feels a new patch is ready for real use, however long that may take.

Benjamin Lee
Melbourne, Australia             "Always real."    http://realthought.net/

Weather outside looks to be 15.1°C, mostly cloudy.
Cold, adj.:
	When the politicians walk around with their hands in their own pockets.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]