From owner-freebsd-questions@FreeBSD.ORG Sat Oct 22 16:27:38 2005 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C13EC16A41F for ; Sat, 22 Oct 2005 16:27:38 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57A0A43D46 for ; Sat, 22 Oct 2005 16:27:38 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id C036B5D6A; Sat, 22 Oct 2005 12:27:37 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 67543-08; Sat, 22 Oct 2005 12:27:37 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-76-130.ny325.east.verizon.net [68.161.76.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id D4DC65CC4; Sat, 22 Oct 2005 12:27:36 -0400 (EDT) Message-ID: <435A6879.5020805@mac.com> Date: Sat, 22 Oct 2005 12:27:37 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Molina Wegener References: <20051022155902.GA43189@daemon.unete.cl> In-Reply-To: <20051022155902.GA43189@daemon.unete.cl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: FreeBSD Questions Subject: Re: send-pr, how pr's are handled X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Oct 2005 16:27:38 -0000 Daniel Molina Wegener wrote: > I have sent a PR (yesterday) with a patch through send-pr, > when I will realize if this one were accepted? That depends on a lot of things. Important patches often get considered in a day or two, ones that are big/complex/etc may take longer. Security issues are also considered at a high priority. It helps to CC: someone responsible for the thing being patched, if there is such a person. In particular, patches sent to a port maintained by nobody can sit for weeks or even months. :-) If you're looking for additional insight, local conventions seem to suggest that one should wait a week after submitting a patch, and then ask about it mentioning the PR #. This gives maintainers who are away on a business trip, vacation, or other aspects of RealJob/RealLife(tm) adequate time to review the PR. If the PR sits for longer than 1 month, bring it up again as a maintainer timeout, if appropriate (ie, a PR about updating a port), or send a short email with the PR # and a description of the issue to one of the higher-level channels like releng, portmgr, etc. -- -Chuck