From owner-freebsd-current@freebsd.org Thu Feb 4 06:58:48 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E86BDA9A205 for ; Thu, 4 Feb 2016 06:58:47 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B9D5A12D4; Thu, 4 Feb 2016 06:58:47 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pf0-x22c.google.com with SMTP id n128so34635304pfn.3; Wed, 03 Feb 2016 22:58:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=b6r/b/jrtQMwgl4GnOxcHIZZOYSeneOpBfiQzS5KfZk=; b=zvO3baYEa9QtUyd7Sf8+FzVSpaLPi7YQ7t1EH9swTcyJxLLmOcemFPh3T2j2zKJh56 wb2mTxXaJeQGCaLd1lu5wkrF2yhZXo5qGeSag2e19mlAsbphXyxPhdF6wyXkQBx0nlvU aRkJAGuujFq3R003bxb7Gm5ZXDIsNcXpU8Av76Nz49k3ix8kRn+S1j/kHVK141qpxRHl 0mViDgxEkeunKZKvZhDJlmmPNpt1glpzxIRE4axw0gcYs73+sFfq3Iybxu7xIgrVG8Ku 4Y2QrNkerSYqiyH+1CIjCrCtQx8au2SvDyYUpWtnN4TicdJ7lfsDF9d+/X/pJKc6Cfqd zszQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:reply-to:subject:references:to:from :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=b6r/b/jrtQMwgl4GnOxcHIZZOYSeneOpBfiQzS5KfZk=; b=YGdkX55xZmf47WNv7qHnj8fDVxHk1aASiXIf5QTAC7uRQ4GWjqlagfb+PiLr7rc15I NUi22oHOv+f5ugXRIfnieuaEI9taNiu9RfhTSS6c0pQBWbuTwK8jvu7E9r/rtkWfD4Wc yiNyiw2nLJgzAmnWtSHNEeGAbjH3hobMU42aaAyTdc+udxugtrSGrofW0INFGzFSOXeq C6g52SPSP0yhSzjyfWoqDP18PTSE65FzjYxtHgjeTI81ekdD4JIW54EF89wyjtDdIA1j XgJ5lN5U1tbqZbAaWLI20IJBvK8q6Csdg0ClfUxm7hwpyHNmRHQaz7I8h27FsMtU0W+A kokQ== X-Gm-Message-State: AG10YOTfo8sOtqMbrqRcWvEh5VyVR9C+xeQx0VBqU1Lu8+MAWYKZc4JMCLtABgnGXdP4pA== X-Received: by 10.98.34.212 with SMTP id p81mr8643822pfj.23.1454569127447; Wed, 03 Feb 2016 22:58:47 -0800 (PST) Received: from ?IPv6:2001:44b8:31ae:7b01:b1ac:464b:e316:e4af? (2001-44b8-31ae-7b01-b1ac-464b-e316-e4af.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:b1ac:464b:e316:e4af]) by smtp.gmail.com with ESMTPSA id z67sm14312543pfa.71.2016.02.03.22.58.45 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 03 Feb 2016 22:58:47 -0800 (PST) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: Requesting MFC's References: <56B2B854.2030904@shrew.net> <56B2EC93.9020409@FreeBSD.org> <56B2F33D.2060106@freebsd.org> To: Allan Jude , freebsd-current@freebsd.org From: Kubilay Kocak Message-ID: <56B2F69E.1000404@FreeBSD.org> Date: Thu, 4 Feb 2016 17:58:38 +1100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Thunderbird/44.0 MIME-Version: 1.0 In-Reply-To: <56B2F33D.2060106@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 06:58:48 -0000 On 4/02/2016 5:44 PM, Allan Jude wrote: > On 2016-02-04 01:15, Kubilay Kocak wrote: >> On 4/02/2016 1:32 PM, Matthew Grooms wrote: >>> All, >>> >>> What is the correct way to request that patches be committed to STABLE? >>> In particular, I'd really like to see these in 10.3-RELEASE as they have >>> been required to build a working firewall in some cases. All are related >>> to problems that were fixed in HEAD, but never MFC'd ... >>> >>> https://svnweb.freebsd.org/base?view=revision&revision=264915 >>> https://svnweb.freebsd.org/base?view=revision&revision=272695 >>> https://svnweb.freebsd.org/base?view=revision&revision=288529 >> >> 1) Create an issue in Bugzilla for it >> a) Assigned to original committer >> b) Set mfc-stableX flag to? >> >> Committer can then set mfc-stableX flag to + when done, or set it to - >> with comment about why not/invalid/inappropriate >> >> If a branch is in feature freeze, issues should either: >> >> - Have re@ CC'd so they can be informed of the request >> - Have maintainer-approval ? re@FreeBSD.org set so that the release >> engineering team can approve/deny changes >> >> This is also the recommended method for changes that already have >> bugzilla issues created for them. >> > > RE@ has a specific procedure for requesting approval for an MFC during a > freeze: https://wiki.freebsd.org/Releng/ChangeRequestGuidelines > I would imagine they prefer not to be added to bugzilla issues until a > committer decides it is worth MFCing something > Yes, sorry.