From: Tom Rini <trini@kernel.crashing.org>
To: Brian Kuschak <bkuschak@yahoo.com>
Cc: Allen Curtis <acurtis@onz.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: bitkeeper changesets
Date: Wed, 4 Sep 2002 16:43:06 -0700 [thread overview]
Message-ID: <20020904234306.GN761@opus.bloom.county> (raw)
In-Reply-To: <20020904172646.94693.qmail@web40202.mail.yahoo.com>
On Wed, Sep 04, 2002 at 10:26:46AM -0700, Brian Kuschak wrote:
>
> --- Tom Rini <trini@kernel.crashing.org> wrote:
> > Revision numbers are not constant. BK keys are.
> > 'bk help key2rev'.
> >
>
> So I assume this is the correct way of getting a
> unique, unchanging revision key corresponding to a
> particular ChangeSet:
>
> bk changes -r1.1091.1.23 -nd:KEY:
> or
> bk prs -r1.1091.1.23 -nd:KEY:
>
> ======== ChangeSet 1.1091.1.23 ========
> paulus@samba.org|ChangeSet|20020803062658|55132
>
> This changeset removes the -rc5 from EXTRAVERSION in
> the top-level Makefile. But I can't I convert this
> key back to the revision number:
>
> echo "paulus@samba.org|ChangeSet|20020803062658|55132"
> |bk key2rev Makefile
>
> Can't find
> paulus@samba.org|ChangeSet|20020803062658|55132 in
> SCCS/s.Makefile
You want to do:
echo "paulus@samba.org|ChangeSet|20020803062658|55132" | bk key2rev ChangeSet
It confused me the first time too. :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-09-04 23:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 21:30 bitkeeper changesets Brian Kuschak
2002-09-04 5:05 ` Allen Curtis
2002-09-04 14:15 ` Tom Rini
2002-09-04 14:42 ` Allen Curtis
2002-09-04 14:57 ` Tom Rini
2002-09-04 17:26 ` Brian Kuschak
2002-09-04 23:43 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-04 16:55 Curtis, Allen
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=20020904234306.GN761@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=acurtis@onz.com \
--cc=bkuschak@yahoo.com \
--cc=linuxppc-embedded@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).