From: Larry McVoy <lm@bitmover.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Larry McVoy <lm@bitmover.com>,
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 09:36:57 -0700 [thread overview]
Message-ID: <20030901163657.GF1327@work.bitmover.com> (raw)
In-Reply-To: <1062434020.14183.13.camel@dhcp23.swansea.linux.org.uk>
On Mon, Sep 01, 2003 at 05:33:40PM +0100, Alan Cox wrote:
> On Llu, 2003-09-01 at 16:59, 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 said "if Linus or Marcelo says
> > do it" specifically for the case that there is some hanky panky going on.
> > On the other hand, it's perfectly possible that the wrong comment got
> > stuck in there and if that's the case why shouldn't it get fixed?
>
> Presumably in the abstract "if you care" case you can generate this
> change globally by excluding that changeset and all after, then
> reapplying it with a different comment then reapplying all that follow ?
Yup, that would work just fine. Anyone can do this.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-09-01 16:37 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
2003-09-01 16:33 ` Alan Cox
2003-09-01 16:36 ` Larry McVoy [this message]
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=20030901163657.GF1327@work.bitmover.com \
--to=lm@bitmover.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albert@users.sourceforge.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.