From owner-freebsd-ports Sat Nov 25 0: 6: 6 2000 Delivered-To: freebsd-ports@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 0787E37B479 for ; Sat, 25 Nov 2000 00:06:04 -0800 (PST) Received: from FreeBSD.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id AAA89392; Sat, 25 Nov 2000 00:05:57 -0800 (PST) (envelope-from DougB@FreeBSD.org) Message-ID: <3A1F72E5.4D46598E@FreeBSD.org> Date: Sat, 25 Nov 2000 00:05:57 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Vladimir Mencl, MK, susSED" Cc: ports@FreeBSD.org Subject: Re: PR 21355 not processed yet References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Vladimir Mencl, MK, susSED" wrote: > > Hello. > > 2 months ago, I submitted a PR (# 21355), concerning the www/evg port. > > I included a patch to fix the problem. > > However, the patch is still not included in the collection of patches > for the port, and the PR is left actually untouched. > > Did I miss something in the procedure of submitting a ports PR? Unfortunately, ports and other kinds of PR's sometimes sit unattended for long periods of time. I looked yours over, and it's not at all clear to me what port you want that patch applied to. Given that I know nothing about python, I can't really make a judgement about that. :) If you could submit a follow-up to your PR with more details, it might get more attention. Good luck, Doug -- So what I want to know is, where does the RED brick road go? Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message