From owner-freebsd-current@freebsd.org Thu Feb 4 06:15:57 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 30BC9A9BD32 for ; Thu, 4 Feb 2016 06:15:57 +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 0187B1A9C for ; Thu, 4 Feb 2016 06:15:57 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pf0-x22c.google.com with SMTP id o185so33627278pfb.1 for ; Wed, 03 Feb 2016 22:15:56 -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=ziwo+vpNKIZ9hz9tCDSWKwV8346CZ0VuKQbj5Y3GblE=; b=UehrD6MmJQN91A7MlWKrrDPIlsXUFeVKhOjXLAsQFNXErr8CrzHI7Sg3fkfNOht4D8 i6spO/LmoQtvflzH1IL80Faf/xUT9Muse9tL+ot+95dwz7C5GZgh4o2ihknE8hRFtqGL LVbieXBspVy7ZtuEMH57APj5qKRdRg7z5in61EyQWFijqGZMszpFv30/OUSIXuyy5R+y 19x/hXouHA+WGDse7kUfOknm8M6KIEDI6IM+BhIAXgsOCWxwYgnZS0NdUOUgGtSEPLl0 EB/HiUKTzJnr8GxjUkUMH849Za8AAkPsepU3BzF1J21mq7iuzbr3rvVS3rB/ji6wD/Np 2RxQ== 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=ziwo+vpNKIZ9hz9tCDSWKwV8346CZ0VuKQbj5Y3GblE=; b=ROSTa3HztxQjX5YYUEH79j/sWeG9utDbgpHWwzczBUcI9LM4tjl6B5DPeuBhWKd6Oq C3OYCF/QTaNDdCaFmN/4qFWvlj5qAQppyaYUGMd8+PkOW0r78QCnz3kge5AqXPdPgNxD +Of73g9PvYXzBzbd1nURx1EZXkQSIld/+X9f9Mozsr+TUHOzVNsOcG7ZdjPJO+IpWv/q DGaAD9ryFWToKWFcvM8A4NhajsuEGdwppZFCQ01zds3sbX1i6ue5O45JKzAKMXKvpU8d yTpUsUImxoL7p+gxae47oioRMk1e1tGz7g0ukQA1t5lGPDEF/Ps6toZ7Tg9g1HWYWk0b opgw== X-Gm-Message-State: AG10YOTmpAyaQl8oT1VDpF8tghl36gpZ4MF8YtpjZPnYlK0i9dPCg/gDL8utVRA3R7o/8Q== X-Received: by 10.98.16.69 with SMTP id y66mr8585799pfi.86.1454566556681; Wed, 03 Feb 2016 22:15:56 -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 s65sm14049901pfi.12.2016.02.03.22.15.55 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 03 Feb 2016 22:15:56 -0800 (PST) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: Requesting MFC's References: <56B2B854.2030904@shrew.net> To: Matthew Grooms , freebsd-current@freebsd.org From: Kubilay Kocak Message-ID: <56B2EC93.9020409@FreeBSD.org> Date: Thu, 4 Feb 2016 17:15:47 +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: <56B2B854.2030904@shrew.net> 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:15:57 -0000 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. > Thanks in advance, > > -Matthew > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"