From owner-freebsd-stable@FreeBSD.ORG Tue Jul 17 03:19:33 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 41701106564A for ; Tue, 17 Jul 2012 03:19:33 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 002208FC1A for ; Tue, 17 Jul 2012 03:19:32 +0000 (UTC) Received: by obbun3 with SMTP id un3so13045128obb.13 for ; Mon, 16 Jul 2012 20:19:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=6iBtJOA2r/+Rxwl5U/p23NBP5NzrRlFYZ6XpmC7IPY8=; b=mACjXgXOtfIVcokZU4BUUQn5G8hWdNNobrMPTSnerPNRWEJxcTCYcxfpgO+3GiX1uT ReZyDHCkMO5THHaAcdPjQy0L8bv7NEAR/t64VFKlyl6ECZRIvdqbmedc7sEl2kmXxSyF rMDo+p32BIaEbWOwO6T9AJ5qXCgxOC9LqPeEQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=6iBtJOA2r/+Rxwl5U/p23NBP5NzrRlFYZ6XpmC7IPY8=; b=dA6L+4n2eGkzVQrzLCrVG7O31Ub0AhEMRUOpeRFlwOkkKkqarHtYT01gpriQNgiTBX 20/Td9ZU2cUo9aTErB4UyhyeJobwl9r8PjNTh42NgKbE8Ih4EfvWPp/0qxc2e+lLXvlN NCTvDJUOjgfqNWekXniGc5FNQmah590DKTHTO7sxwp5DY4s3gF17KMbz2nLd9jrz1MNL a/KsKZWgSS9XACk57CtUBRUoR5OyfH+9AAn1pgtZsKtUx1ze6Lc5aD3HPYnjvaYyk2Kj LEiLRJERMoHoPIlF7GhFzAQEkwLUcJGrOrtvnn6ELbYLNuzora2goq90JpO68V2BzlBl hwxQ== Received: by 10.182.88.9 with SMTP id bc9mr1133465obb.4.1342495172606; Mon, 16 Jul 2012 20:19:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.125.70 with HTTP; Mon, 16 Jul 2012 20:19:02 -0700 (PDT) In-Reply-To: References: From: Eitan Adler Date: Mon, 16 Jul 2012 20:19:02 -0700 Message-ID: To: Trent Nelson Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQm9cfH4+51UfGHcvPqFMVdBM7i1wHHVLFl2j3ZCf8i079J6u7rK2OfZfAv0lipX9Yap7RJA Cc: "freebsd-stable@freebsd.org" Subject: Re: The MFC process... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2012 03:19:33 -0000 On 16 July 2012 19:33, Trent Nelson wrote: > > There are currently no automated MFC systems in place, correct? I.e. the > onus is completely on the developer that made the change to head to merge > back to stable? Correct. > Do the RELENG team do anything in particular to check > that changes for MFC actually make it back to stable? As far as I am aware, they do not. > Reason for asking, I noticed a bit of disparity between dev/isp between > head and stable/9: > ... > I'm currently running a local tree with those revs merged in manually > (simply via `svn merge svn://svn.freebsd.org/base/head/sys/dev/isp .` in > /usr/src/sys/dev/isp), but it'd be nice to get them into 9.1, as they're > all past their recommend soak time (except for that last one, which is a > typo fix). We are currently in a code freeze for 9.1 so no unapproved MFCs may be committed. > Anyway, that got me thinking about the MFC process, especially leading up > to another release, hence this e-mail. What's the preferred way for > non-committers to bring outstanding MFCs to the attention of committers? Exactly the way you did it here: a polite email. :) -- Eitan Adler