From owner-freebsd-commit  Tue Oct 17 13:08:15 1995
Return-Path: owner-commit
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA05444
          for freebsd-commit-outgoing; Tue, 17 Oct 1995 13:08:15 -0700
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA05432
          for cvs-all-outgoing; Tue, 17 Oct 1995 13:08:09 -0700
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA05422
          for cvs-ports-outgoing; Tue, 17 Oct 1995 13:08:05 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA05416
          ; Tue, 17 Oct 1995 13:07:55 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id NAA08632; Tue, 17 Oct 1995 13:07:22 -0700
Date: Tue, 17 Oct 1995 13:07:22 -0700
Message-Id: <199510172007.NAA08632@silvia.HIP.Berkeley.EDU>
To: ache@astral.msk.su
CC: CVS-commiters@freebsd.org, cvs-ports@freebsd.org
In-reply-to: <nmsyuWmCL1@ache.dialup.demos.ru>
Subject: Re: cvs commit: ports/audio/tracker/pkg COMMENT
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-commit@freebsd.org
Precedence: bulk

 * >Andrey, please please please don't do any upgrades until the 2.1 CD is
 * >out!  How many times do I have to say this.... :<
 * 
 * Well, if found your very recent letter about allowing commit of new
 * things and about NO_* targets too:

Duuh, now I know what went wrong.... :<

 * Subject: Re: Can I commit new ports now?
                             ^^^^^^^^^
We've been using "new ports" to mean, well, totally new ports, not
upgrades.  New ports don't screw up my (already built) ports tree
too much so I've been allowing them, upgrades do (to varying extent),
so I've been very careful about them.

Satoshi

 * P.S. Can you do something with the *.language Makefiles?  Will they
 *    work if you change all the empty targets to NO_*?

This doesn't mean you can modify bsd.port.mk at this point of the
game.  During the CONFIGURE_ENV debate, I thought I've been clear
enough that I wanted you to fix ports within the ports tree, without
changing bsd.port.mk! :<