From owner-freebsd-questions Tue Oct 6 14:12:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22167 for freebsd-questions-outgoing; Tue, 6 Oct 1998 14:12:38 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22055 for ; Tue, 6 Oct 1998 14:12:07 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id OAA03462; Tue, 6 Oct 1998 14:11:45 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 6 Oct 1998 14:11:44 -0700 (PDT) From: Doug White To: Sheldon Hearn cc: questions@FreeBSD.ORG Subject: Re: PR's without [PATCH] in synopsis In-Reply-To: <15612.907534738@axl.training.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 4 Oct 1998, Sheldon Hearn wrote: > > Hi folks, > > Recently, a li'l birdie told me that it's a good idea to put text in the > synopsis of PR's that indicates the PR's contain patches, and aren't > just bug reports without suggested fixes. The examples were "[PATCH]" > and "[DIFFs supplied]". > > The reasoning was that there are times when a committer may decide to > spend a little time clearing out PR's but may not feel like doing hard > work. In such cases, the committer might look for text in synopses of > PR's that would indicate "easy commits". > > I've submitted a couple of PR's which would constitute "easy commits" > and I'm wondering whether there's a way to change the synopsis of a > submitted PR. Any ideas? Only committers and others with freefall access can change the synopses. > If not, is there a way to bring to the attention of committers the fact > that my existing PR's include patches without seeming rude or pushy? > Obviously, in the future I'll ensure that my PR synopses contain "easy > commit" indicators. If you think they're 'must be for 3.0' material bring them to the attention of hackers@freebsd.org. Obviously put the PR numbers in or you're going to get laughed at. If they're documentation-related, I'll take a look at it. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message