Robert Collins wrote:
> The cause is that the branch object for 'link' has not followed the
> symlink
I disagree that following the symlink is The Right Thing.
The symlink may well be a versioned file, so the containing directory is
the correct place to search. This allows "bzr log link" to give the
version history of the symlink, while bzr log "subproject/subtree" will
give the version history of the subtree.
Following the symlink would mean that there would be no way to get the
version history of the symlink, and would have even worse effects with
"commit", "merge", "revert" et al.
In sum, symlinks are first-class entities in Bazaar, so it does not make
sense to follow them.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robert Collins wrote:
> The cause is that the branch object for 'link' has not followed the
> symlink
I disagree that following the symlink is The Right Thing.
The symlink may well be a versioned file, so the containing directory is subtree" will
the correct place to search. This allows "bzr log link" to give the
version history of the symlink, while bzr log "subproject/
give the version history of the subtree.
Following the symlink would mean that there would be no way to get the
version history of the symlink, and would have even worse effects with
"commit", "merge", "revert" et al.
In sum, symlinks are first-class entities in Bazaar, so it does not make
sense to follow them.
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFGkjpJ0F+ nu1YWqI0RAlkjAJ 4uL8uNBIUqJlaZP xnjsUToWbup3wCf Yv62 Vx/vjvy0=
mbNwtLIDe8StDNR
=41Yi
-----END PGP SIGNATURE-----