From owner-freebsd-ports Tue Jul 14 06:56:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05513 for freebsd-ports-outgoing; Tue, 14 Jul 1998 06:56:44 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05504 for ; Tue, 14 Jul 1998 06:56:39 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.0/8.9.0) with SMTP id IAA11038; Tue, 14 Jul 1998 08:55:22 -0500 (CDT) Date: Tue, 14 Jul 1998 08:55:22 -0500 (CDT) From: Steve Price To: Adrian Penisoara cc: ports@FreeBSD.ORG Subject: Re: a proliferation of pines In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 14 Jul 1998, Adrian Penisoara wrote: [...] # There are 2 PRs pending on this, you should use them in the mean time: # * ports/7248 for Pine 4.00 (get the *second* set of files, see # Audit-trail !) # * ports/7252 for Pine 3.96 (MASTER_SITES update) # # # Someone (Asami, Steve ?) please review these PRs, it's getting annoying # for many people to get a broken pine tree ! I had intended to do them last weekend, until I saw Andrey Chernov's (it was a committer anyway sorry for not remembering the name exactly) messages about how he was the maintainer and would be taking care of it; although it appeared this port was being maintained by ports@FreeBSD.ORG. I try not to make changes to ports (via PRs) without first giving the maintainer a chance to make the commit themselves. If the maintainer doesn't care and (possibly) doesn't have the time I can do it. I think at least 7252 should go in. And if the pine4 port is not marken broken (hmm...) it should be until things work themselves out. Just my $0.02. Steve # Thank you, # Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message