:In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
:>    There's another good reason to MFC the linux patch on wednesday... 
:>    that is, to do it at the same time the SMP cleanup is MFC'd, and that
:>    is because both patch sets require the linux kernel module to be 
:>    recompiled and I'd rather not force people to do that twice. 
:Matt, this is not a valid reason either.
:Unless there is *urgent* and *overriding* reasons, and that basically
:means that the security-officer says so, all changes must be shaken
:out in -current first.
:That's just the way it is Matt.  Get used to it.
:Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20

   I think you're confused, Poul.  I've gone over the commits made
   to the tree by people over the last few months and frankly there
   are dozens of simultanious -current and -stable commits.  A quick
   check shows that most of them are trivial bug fixes.  

   I will also point out that the current STABLE and CURRENT trees are
   being treated as a special case.  Jordan himself said so!  And that
   he has made a specific statement indicating that people could
   develop in the 4.x tree due to the potential breakage in the 5.x

   This seems entirely appropriate to me.  If the rules have changed since
   that announcement, then I recommend that core make an official statement
   to correct it.

                                        Matthew Dillon 
                                        <[EMAIL PROTECTED]>

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to