From owner-freebsd-stable@FreeBSD.ORG Mon Nov 21 19:21:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50C4A16A41F for ; Mon, 21 Nov 2005 19:21:32 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 313BD43D9D for ; Mon, 21 Nov 2005 19:21:21 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id D460C2B15; Mon, 21 Nov 2005 13:21:07 -0600 (CST) Date: Mon, 21 Nov 2005 13:21:07 -0600 To: Dominic Marks Message-ID: <20051121192107.GD11355@soaustin.net> References: <43820E84.3080000@umn.edu> <200511212014.12716.dom@goodforbusiness.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511212014.12716.dom@goodforbusiness.co.uk> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: Alan Amesbury , freebsd-stable@freebsd.org Subject: Re: Getting a patch integrated into -STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2005 19:21:32 -0000 On Mon, Nov 21, 2005 at 08:14:12PM +0000, Dominic Marks wrote: > On Monday 21 November 2005 18:14, Alan Amesbury wrote: > > Last week I sent a patch in to fix a problem with 'du' (bug report > > #89090). Unfortunately, I failed to indicate in the synopsis line > > that I'd included a patch (albeit one that should probably be looked > > at by someone with more clue than me). Is there a) an easy way for > > me to update the bug report to indicate this, and b) is there a > > typical time-to-fix for this sort of thing? > > send-pr and no :) Please, do not send-pr a completely new PR for something like this. Send email to bugmaster@ instead and we'll fix it. mcl