Date: Wed, 6 Jan 1999 12:32:20 +0100 (CET) From: Søren Schmidt <sos@sos.freebsd.dk> To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Cc: sos@FreeBSD.ORG, msmith@FreeBSD.ORG, current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: syscons update - when? Message-ID: <199901061132.MAA05593@sos.freebsd.dk> In-Reply-To: <199901060314.MAA27736@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Jan 6, 1999 12:14:45 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
It seems Kazutaka YOKOTA wrote: > As I announced before, reorganization of syscons code is under way and > I intend to commit changes in three stages. > > Stage 1: keyboard driver split > Stage 2: video driver split, splash screen > Stage 3: other reorganization > > The new code has been running on my -current box for quite a while. > > Now, -stable branch date is coming up. The question is how much > change we should commit before the branch? We can defer commit after > the branch and later backport the new code from -current to -stable. > However, there is a snug. > > At stage 1 and 2, the users will be forced to change their kernel > configuration files because keyboard and video drivers become separate > from syscons. Such change is probably too much, if suddenly > introduced to -stable well after the branch. > > So, probably our options are: > > a) Commit stage 1 and 2 changes now. Stage 3 changes may be backported > to -stable from -current later. > b) Don't commit any changes now, but commit them to -current after the > branch. Don't backport the changes to -stable at all. When the next > branch (3.1-STABLE?) comes, let it have the new code. > > I prefer the option a). But, I have to expect rough ride after > commits, as changes of this scale will have many initial glitches... I prefer option a) also. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901061132.MAA05593>