From owner-freebsd-stable Sun Sep 17 2:41:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id B482E37B423; Sun, 17 Sep 2000 02:41:55 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8H9fk608081; Sun, 17 Sep 2000 02:41:46 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Garance A Drosihn Cc: Kris Kennaway , freebsd-stable@FreeBSD.ORG Subject: Re: I'll be rolling a 4.1.1 release on September 25th In-Reply-To: Message from Garance A Drosihn of "Sat, 16 Sep 2000 21:36:37 EDT." Date: Sun, 17 Sep 2000 02:41:46 -0700 Message-ID: <8077.969183706@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You left out the exact steps on how someone who does not have > commit privs is supposed to "get their patch applied". I, for > one, have found that process frustrating. If I may try and distill this entire discussion down to a single concrete "action item" which serves everyone's purposes without attempting to negate reality in any way: What we appear to need here is a "How to get something into FreeBSD" FAQ or tutorial which essentially codifies the instructions on how and where to bother developers and how, this being the volunteer world of free software and all, you also run the risk of never getting your patch in at all. That way nobody would have any unrealistic expectations of the process or feel that insult to injury had just been added when told to do something they may have already done. In significant cases, it might even net us some more committers. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message