[PATCH][BUG] The 'bzr check' command doesn't check the merged revision

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Goffredo Baroncelli wrote:
> On Wednesday 07 September 2005 21:31, Aaron Bentley wrote:

>>Checking them is fine, but merged revisions aren't guaranteed to be
>>present in storage, so you should not treat their absence as an error.
> 
> 
> How it is possible to merge some revisions without storing these into the repository ?

When you merge a revision, you implicitly merge its parent revisions,
too.  So you don't need to have access to the parent revisions.

While we do now fetch as many ancestors as we can, this is a new feature
as of 0.7.  Also, I expect that applying changesets will be a common way
of merging revisions without merging all their ancestors.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDIHtq0F+nu1YWqI0RApJeAJ96fVQbUrKfQTXYEuIZsRKFgNxwPwCfeR7c
SjvxC2yr7upLdHghpmiKNIA=
=t/zU
-----END PGP SIGNATURE-----