[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnu-arch-users] address@hidden: Re: bitkeeper comments]
From: |
Zack Brown |
Subject: |
[Gnu-arch-users] address@hidden: Re: bitkeeper comments] |
Date: |
Tue, 9 Sep 2003 16:09:32 -0700 |
User-agent: |
Mutt/1.5.4i |
Looked interesting. What's the tla take on retroactively modifying
the changelog?
Be well,
Zack
----- Forwarded message from Linus Torvalds <address@hidden> -----
To: Christoph Hellwig <address@hidden>
cc: Larry McVoy <address@hidden>,
Albert Cahalan <address@hidden>,
Larry McVoy <address@hidden>,
linux-kernel mailing list <address@hidden>,
address@hidden
Subject: Re: bitkeeper comments
From: Linus Torvalds <address@hidden>
Date: Mon, 1 Sep 2003 09:59:58 -0700 (PDT)
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to address@hidden
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
----- End forwarded message -----
--
Zack Brown
- [Gnu-arch-users] address@hidden: Re: bitkeeper comments],
Zack Brown <=