From: Larry McVoy <lm@bitmover.com>
To: Eugene Surovegin <ebs@innocent.com>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Bitkeeper changeset numbering glitch in 2_4_devel tree
Date: Sun, 28 Jul 2002 07:40:09 -0700 [thread overview]
Message-ID: <20020728074009.D9612@work.bitmover.com> (raw)
In-Reply-To: <5.1.0.14.2.20020727122936.02ababf0@pop.prodigy.net>; from ebs@innocent.com on Sat, Jul 27, 2002 at 12:48:32PM -0700
> What today shows up as changeset 1.1155 may in future become something like
> 1.1088.1.30. I'm sure that Bitkeeper uses other way of identification
> internally but it's not user accessible.
The internal names are called keys or inodes and you get at them with
bk prs -hr<whatever> -nd:KEY: <filename>
In general, anywhere you can use a revision, you may use a key instead.
Nt in BK/web yet though.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-07-28 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 19:48 Bitkeeper changeset numbering glitch in 2_4_devel tree Eugene Surovegin
2002-07-28 14:40 ` Larry McVoy [this message]
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=20020728074009.D9612@work.bitmover.com \
--to=lm@bitmover.com \
--cc=ebs@innocent.com \
--cc=linuxppc-dev@lists.linuxppc.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).