From owner-freebsd-bugbusters@FreeBSD.ORG Tue Dec 25 10:28:14 2012 Return-Path: Delivered-To: freebsd-bugbusters@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C5BDD5B7 for ; Tue, 25 Dec 2012 10:28:14 +0000 (UTC) (envelope-from dbtedman@gmail.com) Received: from mail-pa0-f48.google.com (mail-pa0-f48.google.com [209.85.220.48]) by mx1.freebsd.org (Postfix) with ESMTP id 8D80D8FC0A for ; Tue, 25 Dec 2012 10:28:14 +0000 (UTC) Received: by mail-pa0-f48.google.com with SMTP id fa1so4447172pad.35 for ; Tue, 25 Dec 2012 02:28:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=qVb+70BVe4mVtOSi98orLA6INx8eUzEoclnjaOl+jIk=; b=oY5IhVQgVAgKVZ+/MPIokQOe/aLVqTzk9PsckxvLsYqAcQPo/+k6j8j5M1RFioew+3 4KF//pfhMJiRHIK5qvx0AxdqcXMgUqWd0WCRliKkqHUICqPERHw/J6iQ1UC2swmfQEB3 DKgHdaaD1Zc1W/zlp7WH9UwMpseQ4L9nOWFDdUv6pa0m9uA1OnuOwoQOtiem2PRvYGwz Pwgvi/5Te0V9t9jsHXRE/VCeluNpsbKDN7/FfzHnUdEFBFveejjYhBzDp/+SLFoFlVev qEMiX9YwqJx4vBkstpdfglUia3MA19MCz0ZzUtiNS7SN0X1UEZY6OO/vxBSbBG5f7tKN Jd/A== X-Received: by 10.66.73.165 with SMTP id m5mr71220027pav.78.1356431293997; Tue, 25 Dec 2012 02:28:13 -0800 (PST) Received: from [192.168.0.100] (CPE-123-211-55-14.lnse3.cha.bigpond.net.au. [123.211.55.14]) by mx.google.com with ESMTPS id vk5sm13891090pbc.34.2012.12.25.02.28.11 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 25 Dec 2012 02:28:13 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: freebsd-bugbusters Digest, Vol 245, Issue 1 From: Daniel Tedman In-Reply-To: Date: Tue, 25 Dec 2012 20:28:14 +1000 Content-Transfer-Encoding: quoted-printable Message-Id: <67637DA9-8C5E-45E7-85BD-632B02F4205A@gmail.com> References: To: freebsd-bugbusters@freebsd.org X-Mailer: Apple Mail (2.1499) X-BeenThere: freebsd-bugbusters@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Coordination of the Problem Report handling effort." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Dec 2012 10:28:14 -0000 On 22/12/2012, at 10:00 PM, freebsd-bugbusters-request@freebsd.org = wrote: > Send freebsd-bugbusters mailing list submissions to > freebsd-bugbusters@freebsd.org >=20 > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-bugbusters > or, via email, send a message with subject or body 'help' to > freebsd-bugbusters-request@freebsd.org >=20 > You can reach the person managing the list at > freebsd-bugbusters-owner@freebsd.org >=20 > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-bugbusters digest..." >=20 >=20 > Today's Topics: >=20 > 1. closing fixed PRs (Mark Johnston) > 2. Re: closing fixed PRs (Eitan Adler) >=20 >=20 > ---------------------------------------------------------------------- >=20 > Message: 1 > Date: Fri, 21 Dec 2012 16:07:55 -0500 > From: Mark Johnston > To: freebsd-bugbusters@freebsd.org > Subject: closing fixed PRs > Message-ID: <20121221210755.GB23513@oddish.home> > Content-Type: text/plain; charset=3Dus-ascii >=20 > Hello, >=20 > There are a few PRs (166994 and 169642 for example) where the reported > issue has been independantly fixed and the submitter doesn't seem to = be > interested in a patch for their tree. What's the right way to handle > them? I don't see any reason for them to stay open. I was thinking of > setting them to feedback mode and waiting a week before closing them. = Is > this alright? >=20 > Thanks! > -Mark >=20 >=20 > ------------------------------ >=20 > Message: 2 > Date: Fri, 21 Dec 2012 16:26:28 -0500 > From: Eitan Adler > To: Mark Johnston > Cc: freebsd-bugbusters@freebsd.org > Subject: Re: closing fixed PRs > Message-ID: > = > Content-Type: text/plain; charset=3DUTF-8 >=20 > On 21 December 2012 16:07, Mark Johnston wrote: >> Hello, >>=20 >> There are a few PRs (166994 and 169642 for example) where the = reported >> issue has been independantly fixed and the submitter doesn't seem to = be >> interested in a patch for their tree. What's the right way to handle >> them? I don't see any reason for them to stay open. I was thinking of >> setting them to feedback mode and waiting a week before closing them. = Is >> this alright? >=20 > If you are sure the reported issue has been fixed please set them to > patched - if it has not yet been MFCed > closed - if it has been MFCed or never will be >=20 > in the message please mention the relevant commit numbers >=20 > please assign them to the committer who fixed it. >=20 > example: >=20 > change-pr -p -T markj -m "fixed in r12345 - will be MFCed shortly" = docs/78965 >=20 >=20 > --=20 > Eitan Adler >=20 >=20 > ------------------------------ >=20 > _______________________________________________ > freebsd-bugbusters@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bugbusters > To unsubscribe, send any mail to = "freebsd-bugbusters-unsubscribe@freebsd.org" >=20 >=20 > End of freebsd-bugbusters Digest, Vol 245, Issue 1 > **************************************************