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

[Aaron Bentley]

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

Goffredo Baroncelli wrote:
> Hi all,
> 
> the merged revision aren't inserted into the .bzr/revision-history. The 'bzr check' command checks only 
> the revisions listed in .bzr/revision-history, so the merged revision aren't checked at all.

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.

> With the patch below the 'bzr check' command checks every revision listed in 
> .bzr/revision-history, and every parent referred by these revisions walking the chain of the revision.
> 
> Does anyone know what is the pourpose of the .bzr/merged-patches ? I think that this file should contains
> the marged revision UUID, but the docs aren't very clear and it seems that the bzr code creats only the
> file and doesn't care anymore.

Its purpose is to indicate which revisions have been merged since the
last commit.  It used during the commit process to produce the correct
list of parents.

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

iD8DBQFDHz/90F+nu1YWqI0RAidHAJ99S4ck1lbwN505pK8mETK0XAUCFwCfbU6s
JbjADLsvf74aobupP9sVQHk=
=eTjf
-----END PGP SIGNATURE-----