>
> Ok, I've merged stuff from more people, and 2.5.44 is out there. We're
> getting closer, folks.
>
> And for the ext 8 days (starting _now_) it is totally unnecessary to try
> to send me patches or cc me on the discussions about what needs to be
> merged or not. I won't read it, and when I get back I will likely just
> flush the whole inbox, since there's no way I can try to catch up _and_
> try to merge some final pieces before the feature freeze at the same time.
Perhaps this is good reason to delay the freeze for an additional 2 weeks or
so? I fail to see the necessity of rushing into a freeze, especially when
it seems obvious that people are trying to merge code which hasn't been
adequately tested. I think Hans Reiser and others have brought up valid
points that the freeze is happening too soon. I tend to agree, especially
looking back at the timetable surrounding 2.1.X development. Since I'm not
a contributor, I know my opinion doesn't count for much. Still, as a user
I think it is important not to write of new features just because they
didn't make the "arbitrary" freeze date. Again, I really don't see what
the rush is all about.
Just my .02 (US),
Nicholas
-
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/