On Dec 14, 2007 8:27 AM, Ray Lee <[EMAIL PROTECTED]> wrote: > On Dec 14, 2007 6:40 AM, <[EMAIL PROTECTED]> wrote: > > Agreed. As a b43legacy maintainer, I'd be happy to know if Ingo > > suggests other ways to smooth out the transition. I haven't read > > proposals yet. > > This isn't rocket science guys. Put a file in somewhere in your tree > called ReleaseAnnouncement or something, and ask Linus to adjust his > kernel release process to include the contents of `cat $( find . -name > ReleaseAnnouncement )` in the release message he sends out. Clear out > the file after the release. > > Include things such as "bcm43xx is scheduled for removal. build both > b43 and b43legacy as a replacement. Be sure to download the latest > firmware from $URL and follow the instructions there to extract the > correct latest firmware necessary for your chip. There are known > incompatibilities with old udev versions, please ensure blah blah > blah."
Or even better, keep the history, and show the diff of the old versus new in the release announcement, with an appropriate sed 's/+/ /' or somesuch. <shrug> I'm sure you all will figure something out. Regardless, my point is a higher level changelog that is human readable would be helpful. (There are thousands of per-commit changelog entries to read, it's beyond what I have the time to do when testing a new kernel). Also, it seems distributing the release announcement work would be as helpful as distributing the code development work. Ray -- 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/
