John A Meinel wrote:
> In theory, this may not be too hard to do. The biggest problem is that
> our revisionspec code is all built around looking them up in the Branch
> or possibly Repository.
We'll need to fix this for the 'current:' revision (which refers to the
working tree) also.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John A Meinel wrote:
> In theory, this may not be too hard to do. The biggest problem is that
> our revisionspec code is all built around looking them up in the Branch
> or possibly Repository.
We'll need to fix this for the 'current:' revision (which refers to the
working tree) also.
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFGw0Ee0F+ nu1YWqI0RAjFOAJ 0QIzg5+ DMJUGPxeZo9+ 4hV4eH15wCfbix+ h15kIheM=
3f/CQsak7d2zWDE
=UwP3
-----END PGP SIGNATURE-----