From owner-freebsd-bugs Sat Nov 25 13:10: 6 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A12A137B4C5 for ; Sat, 25 Nov 2000 13:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id NAA62079; Sat, 25 Nov 2000 13:10:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sat, 25 Nov 2000 13:10:02 -0800 (PST) Message-Id: <200011252110.NAA62079@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Mike Meyer Subject: Re: misc/23094: The PR system has no way to let committers know that a PR includes commitable code Reply-To: Mike Meyer Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/23094; it has been noted by GNATS. From: Mike Meyer To: Bill Fumerola Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: misc/23094: The PR system has no way to let committers know that a PR includes commitable code Date: Sat, 25 Nov 2000 15:07:29 -0600 (CST) Mike Meyer types: > Bill Fumerola types: > > On Sat, Nov 25, 2000 at 08:13:22PM -0000, mwm@mired.org wrote: > > > >Category: misc > > > >Synopsis: The PR system has no way to let committers know that a PR includes commitable code > > typically, one uses [PATCH] at the beginning of "synopsis" to indicate > > that a patch is in the PR. > Is this documented anywhere? What about man pages, FAQ submission > (though those are the exceptions to this problem), and new ports? In thinking about it, documenting that in the block of text at the top of the pr page would certainly solve the problem.