From owner-freebsd-current Wed Jan 6 03:34:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00168 for freebsd-current-outgoing; Wed, 6 Jan 1999 03:34:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00159; Wed, 6 Jan 1999 03:34:08 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id MAA05593; Wed, 6 Jan 1999 12:32:20 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199901061132.MAA05593@sos.freebsd.dk> Subject: Re: syscons update - when? In-Reply-To: <199901060314.MAA27736@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Jan 6, 1999 12:14:45 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Wed, 6 Jan 1999 12:32:20 +0100 (CET) Cc: sos@FreeBSD.ORG, msmith@FreeBSD.ORG, current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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