'bzr blame' fails with ghost revisions and 'bzr check' output...

[John Szakmeister]

One of the members on my team ran across an issue when running blame
with ghost revisions (and it looks like there is an open ticket about
running 'bzr diff' when one of the revs is a ghost too).  I reproduced
the issue, and ran 'bzr check' against the new branch (one with a
ghost rev in it).  I'm not sure I understand the output:
    Checking working tree at '/Users/jszakmeister/projects/tmp/new-trunk'.
    Checking branch at 'file:///Users/jszakmeister/projects/tmp/new-trunk/'.
    Checking repository at 'file:///Users/jszakmeister/projects/tmp/new-trunk/'.
    checked repository <bzrlib.transport.local.LocalTransport
url=file:///Users/jszakmeister/projects/tmp/new-trunk/> format
<RepositoryFormat2a>
         4 revisions
         2 file-ids
         1 ghost revisions
         1 inconsistent parents
    checked branch file:///Users/jszakmeister/projects/tmp/new-trunk/
format Branch format 7

I'm a bit confused about the inconsistent parents line.  What does
that mean?  There's nothing in the help that mentions this... but it
seems bad.  Can someone please explain what it means?

Thanks!

-John