Re: Bzr Emacs question

[Bill Wohler <wohler@newt.com>]

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Sat, 24 Nov 2012 09:02:09 -0800
>> From: Bill Wohler <wohler@newt.com>
>> 
>> I want to make an MH-E 8.3.1 release that corresponds to the Emacs 24.1
>> release. I thought that I would do this:
>> 
>>     bzr tag -r emacs-24.1 mh-e-8.3.1
>> 
>> But then when I run the following to get the proper workspace for
>> creating a release:
>> 
>>     bzr up -r mh-e-8.3.1
>> 
>> I get this error:
>> 
>>     bzr: ERROR: branch has no revision cyd@gnu.org-20120610074146-e2dmv3euiqbajrxt                        
>>     bzr update --revision only works for a revision in the branch history
>> 
>> What is wrong?
>
> A tag is not a revision-id by itself.  Try
>
>   bzr up -r tag:mh-e-8.3.1

Not surprisingly, that produces the same error. Note that "bzr help
revisionspec" says:

    Alternately, [the revision] can be given without a keyword, in which
    case it will be checked as a revision number, a tag, a revision id,
    a date specification, or a branch specification, in that order.

> (And I'm not sure you really want "up" and not some other command, but
> that's another story.)

What would you recommend as an alternative to "svn up -r<revision>"?

>> On a related note, what command should I use to confirm the revision of
>> the workspace? "svn info" provides this information but "bzr info" does
>> not.
>
> Does "bzr revno" do what you want?

I think so. After running "bzr up -r 108549" (the master revision that
contains a merge of emacs-24.1), the --tree option was needed to show
that version. Without --tree, the version for the head of the trunk was
shown:

    $ bzr revno --tree
    108549
    $ bzr revno 
    111000

Thanks!

-- 
Bill Wohler <wohler@newt.com> aka <Bill.Wohler@nasa.gov>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD