On Tue, 25 Jan 2005, Bill Davidsen wrote:
>
> Unfortunately if A depends on B to work at all, you have to put A and B
> in as a package.
No. That's totally bogus. You can put in B on its own. You do not have to
make A+B be one patch.
> There is no really good way (AFAIK) to submit a bunch of patches and
> say "if any one of these is rejected the whole thing should be ignored."
But that's done ALL THE TIME. Claiming that there is no good way is not
only disingenious (we call them "numbers", and they start at 1, go to 2,
then 3. Then there's usually a 0-patch which only contains explanations
of the series), but it's clearly not true, since we have patches like that
weekly.
In the last seven days the kernel mailing list has seen at least four
such series where patches depend at least partly on each other:
- Kay Sievers: driver core: export MAJOR/MINOR to the hotplug (0-7)
- Andreas Gruenbacher: NFSACL protocol extension for NFSv3 (0-13)
- Roland Dreier: InfiniBand updates for 0-12
- Roland McGrath: per-process timers (1-7)
and that was from just a quick look. It seems to be almost a daily
occurrence.
In short: listen to Arjan, because he is wise. And stop making totally
idiotic excuses that are clearly not true.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
