Martin von Gagern wrote:
> Public bug reported:
>
>>From the user point of view, this feels like a variation of bug #496590,
> while the internal cause is probably the same as in bug #144421.
>
>
> You probably want to write a bunch of test cases, ensuring that branch:
> revspecs work for all commands.
>
> ** Affects: bzr
> Importance: Undecided
> Status: New
>
A workaround is "bzr log -r -1:../trunk".
Though that only works if the trunk revision is already present in the
local repository.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin von Gagern wrote:
> Public bug reported:
>
>>From the user point of view, this feels like a variation of bug #496590,
> while the internal cause is probably the same as in bug #144421.
>
>
> You probably want to write a bunch of test cases, ensuring that branch:
> revspecs work for all commands.
>
> ** Affects: bzr
> Importance: Undecided
> Status: New
>
A workaround is "bzr log -r -1:../trunk".
Though that only works if the trunk revision is already present in the
local repository.
John enigmail. mozdev. org/
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAks qQYIACgkQJdeBCY SNAAOGwwCgq4JHD aVMLsA/ 2yB0UImSEJbx 5q0s71WtjyWg898 R5ND
pTMAnRuig28H+
=ho5N
-----END PGP SIGNATURE-----