From: Larry McVoy <lm@bitmover.com>
To: Albert Cahalan <albert@users.sourceforge.net>
Cc: Larry McVoy <lm@bitmover.com>,
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 08:46:46 -0700 [thread overview]
Message-ID: <20030901154646.GB1327@work.bitmover.com> (raw)
In-Reply-To: <1062430014.314.59.camel@cube>
On Mon, Sep 01, 2003 at 11:26:55AM -0400, Albert Cahalan wrote:
> I'm OK with whatever ensures that somebody looking back
> through the BitKeeper logs isn't going to come to the
> conclusion that I broke something.
>
> Um, not everybody will grab updates from bkbits.net,
> right? Pardon me for being clueless about BitKeeper,
> but is there some command Andi or Linus could run?
Unfortunately the checkin comments themselves are not revision controlled.
You have to run a command on each repository that needs to be fixed,
if you send me the desired comments I'll post the command. Then if
Linus or Marcelo says do it I'll do it on bkbits.net. That should be good
enough, the logs there are what people tend to browse.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-09-01 15:46 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 [this message]
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
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=20030901154646.GB1327@work.bitmover.com \
--to=lm@bitmover.com \
--cc=ak@suse.de \
--cc=albert@users.sourceforge.net \
--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 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).