From: Larry McVoy <lm@bitmover.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Rik van Riel <riel@conectiva.com.br>,
Christoph Hellwig <hch@caldera.de>,
lm@bitmover.com, hpa@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 bitkeeper repository
Date: Fri, 22 Feb 2002 17:32:22 -0800 [thread overview]
Message-ID: <20020222173222.E11156@work.bitmover.com> (raw)
In-Reply-To: <20020222193723.GL719@opus.bloom.county> <Pine.LNX.4.33L.0202221648320.7820-100000@imladris.surriel.com> <20020223003513.GM719@opus.bloom.county>
In-Reply-To: <20020223003513.GM719@opus.bloom.county>; from trini@kernel.crashing.org on Fri, Feb 22, 2002 at 05:35:13PM -0700
On Fri, Feb 22, 2002 at 05:35:13PM -0700, Tom Rini wrote:
> > You forgot about setting the proper BK_USER, BK_HOST and
> > 'bk comment' commands ;)
>
> heh. Those are rather new things, aren't they? :) Anyhow, the goal for
> these tree(s) is to keep the PPC children trees up to date.
BK_USER, BK_HOST have been around forever but their use is discouraged for
the following reason: BK is a distributed system, we need unique names for
things, and the user&host are part of the name we make up.
bk comments is new and a darned useful thing, too, I'm glad Linus asked
for it. You just have to read the man page and realize that your updates
to the comments may not propogate.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-02-23 1:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 15:06 Linux 2.4 bitkeeper repository Christoph Hellwig
2002-02-22 15:13 ` Jeff Garzik
2002-02-22 15:26 ` DevilKin
2002-02-22 15:40 ` Jeff Garzik
2002-02-22 15:44 ` Stelian Pop
2002-02-22 16:36 ` Marcelo Tosatti
2002-02-22 18:42 ` Larry McVoy
2002-02-22 19:37 ` Rik van Riel
2002-02-22 19:45 ` Larry McVoy
2002-02-23 19:40 ` Linus Torvalds
2002-02-22 16:53 ` Larry McVoy
2002-02-22 19:26 ` Rik van Riel
2002-02-22 19:37 ` Tom Rini
2002-02-22 19:49 ` Rik van Riel
2002-02-23 0:35 ` Tom Rini
2002-02-23 1:32 ` Larry McVoy [this message]
2002-02-23 1:46 ` Davide Libenzi
2002-02-23 1:58 ` Larry McVoy
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=20020222173222.E11156@work.bitmover.com \
--to=lm@bitmover.com \
--cc=hch@caldera.de \
--cc=hpa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=trini@kernel.crashing.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.