From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Larry McVoy <lm@bitmover.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Albert Cahalan <albert@users.sourceforge.net>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>,
ak@suse.de
Subject: Re: bitkeeper comments
Date: Mon, 1 Sep 2003 18:22:46 +0200 (MEST) [thread overview]
Message-ID: <Pine.GSO.4.21.0309011820010.5048-100000@waterleaf.sonytel.be> (raw)
In-Reply-To: <20030901161144.GD1327@work.bitmover.com>
On Mon, 1 Sep 2003, Larry McVoy wrote:
> On Mon, Sep 01, 2003 at 05:02:18PM +0100, Christoph Hellwig wrote:
> > On Mon, Sep 01, 2003 at 08:59:15AM -0700, Larry McVoy wrote:
> > > Hey, I'm not in the middle of this because I don't understand who is right
> > > and it's not my place to make that call.
> >
> > I doesn't matter who's actually right. If Andi was wrong Albert can
> > demand a apology from him or sue him or whater (not that his name is
> > actually mentioned in the message).
> >
> > But we're not going to retroactively censor commit messages.
>
> I'm confused, I thought Linus/Marcelo/Andrew were the tree maintainers.
> As long as they are they get to make the call, not you (or me or whoever).
Retroactively changing a commit message may be a dangerous precedent. While
there may be legitimate reasons (E.g. plain wrong comments or `actually this
part was not written by x but by y'), one day The Evil Empire may claim we
changed the evidence of who did what.
Putting comments under revision control is another option, but may be too
deep-involving...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2003-09-01 16:24 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 [this message]
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
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=Pine.GSO.4.21.0309011820010.5048-100000@waterleaf.sonytel.be \
--to=geert@linux-m68k.org \
--cc=ak@suse.de \
--cc=albert@users.sourceforge.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@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).