Subject: Re: Suggestion re: [PATCH] Remove Bitkeeper documentation from Linux tree
To: phillips@bonn-fries.net (Daniel Phillips)
Date: Sun, 21 Apr 2002 15:08:59 -0700 (PDT)
Cc: lm@bitmover.com (Larry McVoy), cat@zip.com.au (CaT),
        aia21@cantab.net (Anton Altaparmakov), linux-kernel@vger.kernel.org
In-Reply-To: <E16yz02-0000lC-00@starship> from "Daniel Phillips" at Apr 20, 2002 07:50:14 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20020421220859.D39E389579@cx518206-b.irvn1.occa.home.com>
From: barryn@pobox.com (Barry K. Nathan)
Sender: linux-kernel-owner@vger.kernel.org

Daniel Phillips wrote:
> Horse, barn.  We need a solution that works before the patch gets applied.

Horse, barn... but horse (patch) is under 24/7 surveillance by one or two
GPS-locator-equipped robots that the horse can't escape from (e-mail
discussion and/or BK changelog entry) so who cares whether it's in the
barn or not? We can find the horse and bring it back to the barn either
way.

Or, to drop the metaphor: We do not *need* a solution that works before
the patch gets applied. It could be desirable, but it's not *necessary*.
Once a BK patch is applied, the code itself is not set in stone; the patch
can be discussed on the list, modified, or reverted (i.e., rejected after
all) just like a patch that was posted to the mailing list and discussed
first.

-Barry K. Nathan <barryn@pobox.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/