> Yes, and I miss why that matters. Let me see if I can make the idea clear
> to you:
> 2.4.22-pre5 some code
> 2.4.22-pre5-bk1 fixes
> 2.4.22-pre5-bk2 more fixes
> 2.4.22-pre5-bk3 still more fixes
> 2.4.22-pre6 fixes to date plus major changes
>
> So when a maintainer got something major it wouldn't go into bk (the
> commercial software database) until a new -pre, while the -bk patches
> available for download would get the fixes only.
What if a fix depends on a major-change-patch? What if a fix is itself a
major change?
-- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/ - 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/
This archive was generated by hypermail 2b29 : Wed Apr 30 2003 - 22:00:22 EST