From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262967AbTIARDK (ORCPT ); Mon, 1 Sep 2003 13:03:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263172AbTIARCk (ORCPT ); Mon, 1 Sep 2003 13:02:40 -0400 Received: from fw.osdl.org ([65.172.181.6]:58531 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S263154AbTIARAU (ORCPT ); Mon, 1 Sep 2003 13:00:20 -0400 Date: Mon, 1 Sep 2003 09:59:58 -0700 (PDT) From: Linus Torvalds To: Christoph Hellwig cc: Larry McVoy , Albert Cahalan , Larry McVoy , linux-kernel mailing list , Subject: Re: bitkeeper comments In-Reply-To: <20030901170218.A24713@infradead.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 1 Sep 2003, Christoph Hellwig wrote: > > But we're not going to retroactively censor commit messages. Actually, I do that all the time. In fact, it was I who asked Larry to add the "bk comment" command in to make it easy to do so. The thing is, it's hard to do after the message has already gone out into the public - but I fix up peoples email commentary by hand both in the email and often later after it has hit my BK tree too. I try to fix obvious typos, and just generally make the things more readable. And if the comment was wrong, then it should be fixed. Not because of any "censorship", but because it's misleading if the comment says it fixes something it doesn't fix - and that might make people overlook the _real_ thing the change does. Linus