[PATCH] Missing revision spec for "bzr version"

[John A Meinel]

Lalo Martins wrote:
> And so says John A Meinel on 17/09/05 11:35...
>
>>Basically, I have something like my home directory automatically
>>versioned, but I'm using the tarball bzr.dev so I don't have the history.
>>
>>In that case, your code would find my working directory as the branch,
>>which would cause it to report the wrong revision.
>
>
> Indeed.  So my code brings back the previous behavior, and yours brings
> back the feature in a better way.  Yours it is then :-)
>
> best,
>                                                Lalo Martins

I merged this into my integration branch, revno 1217. However, I wanted
to add tests for it, but I can't think of what the correct way to do it
would be.

The problem is that "bzr version" won't print out that information if
you have the snapshot/release, and I think we want all tests to pass,
even in a release.

So what should the test case look like? Should it check for a ".bzr"
directory at the same level as bzrlib, and if it exists, check the
output of bzr version to make sure that it has a revision identifier,
and then run bzr revno in the same directory to make sure that it matches?

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050917/5af62783/attachment.pgp