A restriction on file formats should not be a major hardship for getting
patches out. Submit it in a suitable format. It is clear that bz2 may not be
a suitable format, as there are some who do not support bz2. Come on, you've
got tar/gz...
That said, it may be appropriate to document this.
> 2) We know that it can't be picked from a CVS archive, or packaged as a
> release from an archive, because
> http://kt.linuxcare.com/kt19990819_31.html#9
This is a misrepresentation of Linus' comments on this subject. Linus was
commenting on the difficulties of incorporating infrequent, large snapshots.
Infrequent, large snapshots ARE inappropriate here, whereas small, frequent
incremental diffs are appropriate - they ease peer review, and they introduce
much less risk. Linus also acknowledged that large snapshots may be
appropriate for things (such as the ISDN functionality) being added to standard
kernels for the first time.
> 3) We know that it can't be sent any time in the next two weeks, because
> http://kernelnotes.org/lnxlists/linux-kernel/lk_9909_02/msg00460.html
Hey, go figure, Linus takes a couple weeks off. Core functionality and new
features need to go through him, and seeing as there's a feature freeze now,
need to be very well justified.
> I just don't see much there to do with the stability, cleanliness and solidity
> criteria Alan mentioned a couple of posts back. In fact, these reasons have
> nothing to do with why people use Linux, and an N-year delay in a minor patch
> is a pretty clear sign that something's awry.
A big delay is concerning. However, the reason Linus went off on the ISDN
group in your second link was to improve stability and solidity. Infrequent
large patches do not do anything positive for stability.
> Yes, I asked. Yes, the author has posted patches. He's probably too polite.
Where were the patches posted? When were the patches posted? How were the
patches posted?
PK
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/