From: Larry McVoy <lm@bitmover.com>
To: Christoph Hellwig <hch@infradead.org>,
Jakob Oestergaard <jakob@unthought.net>,
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 10:40:32 -0700 [thread overview]
Message-ID: <20030901174032.GD16620@work.bitmover.com> (raw)
In-Reply-To: <20030901182827.A26176@infradead.org>
On Mon, Sep 01, 2003 at 06:28:27PM +0100, Christoph Hellwig wrote:
> On Mon, Sep 01, 2003 at 07:23:34PM +0200, Jakob Oestergaard wrote:
> > 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.
>
> Yupp, that's what I meant. I certainly don't want a thought police
> on my source trees.
Trivial w/ the current BK because the comments aren't versioned. Just have
someone be elected as the archiver and have them have a cron job which pulls
bkbits.net every 20 minutes or so. Then if the comments are ever changed
your archive will have the originals.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-09-01 17:42 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
2003-09-01 17:28 ` Christoph Hellwig
2003-09-01 17:40 ` Larry McVoy [this message]
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=20030901174032.GD16620@work.bitmover.com \
--to=lm@bitmover.com \
--cc=ak@suse.de \
--cc=albert@users.sourceforge.net \
--cc=hch@infradead.org \
--cc=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.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).