linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Larry McVoy <lm@work.bitmover.com>,
	Albert Cahalan <albert@users.sourceforge.net>,
	Larry McVoy <lm@bitmover.com>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	ak@suse.de
Subject: Re: bitkeeper comments
Date: Mon, 1 Sep 2003 19:23:34 +0200	[thread overview]
Message-ID: <20030901172334.GE14716@unthought.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0309010956390.7908-100000@home.osdl.org>

On Mon, Sep 01, 2003 at 09:59:58AM -0700, Linus Torvalds wrote:
> 
> 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.

There is an important difference.

If I send you a mail saying "X" and you change it to say "Y" and put "Y"
in the source tree, fine.  It was a mail between us, noone except you
and me will know.  If I think it's wrong, maybe I can make you submit
"X" to the source tree instead, with an explanation.

Everything that was ever publicly visible, stays publicly visible, even
with the the revised comments, thanks to the revision history.

But changing the source tree revision history retroactively, that's bad.
It defies the purpose of revision control itself.

The source tree is a public record. People will remember "this said 'Y'
I'm sure, but now it says 'X', why is that?" - and noone can answer.
History forgotten.

It's your call, but I can certainly see why some feel bad about this.

After all, we wouldn't want to edit the e-mail archives to remove all
trace of what happened, either, would we?   ;)

Cheers,

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:

  reply	other threads:[~2003-09-01 17:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-01  4:15 bitkeeper comments Albert Cahalan
2003-09-01 14:07 ` Larry McVoy
2003-09-01 15:26   ` Albert Cahalan
2003-09-01 15:46     ` Larry McVoy
2003-09-01 15:56       ` Christoph Hellwig
2003-09-01 15:59         ` Larry McVoy
2003-09-01 16:02           ` Christoph Hellwig
2003-09-01 16:11             ` Larry McVoy
2003-09-01 16:22               ` Geert Uytterhoeven
2003-09-01 16:15             ` Andi Kleen
2003-09-01 16:59             ` Linus Torvalds
2003-09-01 17:23               ` Jakob Oestergaard [this message]
2003-09-01 17:28                 ` Christoph Hellwig
2003-09-01 17:40                   ` Larry McVoy
2003-09-01 16:33           ` Alan Cox
2003-09-01 16:36             ` Larry McVoy
2003-09-01 16:59       ` Bug in linux-2.6.0-test4 ? dada1
2003-09-01 18:08       ` bitkeeper comments Albert Cahalan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030901172334.GE14716@unthought.net \
    --to=jakob@unthought.net \
    --cc=ak@suse.de \
    --cc=albert@users.sourceforge.net \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=lm@work.bitmover.com \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).