Jelmer Vernooij wrote:
> Just reproduced this. It looks like this particular code path triggers
> some inefficiencies in the file id generation code. ("bzr log" without
> arguments should be quick)
>
> For now, you may be better of creating a bzr branch of the repository
> and using "bzr log" in that rather than working in a svn working copy.
> This is relatively fast, here at least:
>
> $ bzr branch http://svn.python.org/projects/peps/trunk peps.bzr
> $ cd peps.bzr
> $ bzr log pep-0345.txt
Thanks for the workaround. Using 'svn log' is another alternative, of
course.
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 <email address hidden>
Palladion Software "Excellence by Design" http://palladion.com
-----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
Jelmer Vernooij wrote: svn.python. org/projects/ peps/trunk peps.bzr
> Just reproduced this. It looks like this particular code path triggers
> some inefficiencies in the file id generation code. ("bzr log" without
> arguments should be quick)
>
> For now, you may be better of creating a bzr branch of the repository
> and using "bzr log" in that rather than working in a svn working copy.
> This is relatively fast, here at least:
>
> $ bzr branch http://
> $ cd peps.bzr
> $ bzr log pep-0345.txt
Thanks for the workaround. Using 'svn log' is another alternative, of
course.
Tres. ======= ======= ======= ======= ======= ======= ======= ======= ==== palladion. com enigmail. mozdev. org
- --
=======
Tres Seaver +1 540-429-0999 <email address hidden>
Palladion Software "Excellence by Design" http://
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFJ+ cAc+gerLs4ltQ4R AvW3AJ9JIRi71o7 5LypQOxhFpmXjBX j6mgCfXTbd 7uLZu6ZU=
gJPTQi9AgP83cVV
=9NQu
-----END PGP SIGNATURE-----