Support for orthogonal history of changesets

[anatoly techtonik]

I am Looking at ChangesetEvolution description:

"set of obsolescence markers describes a history of changeset
modifications that is orthogonal to the repository history of file
modifications"

There are two questions:

1. about markers with their own history for changesets

Is there a way to provide and exchange alternative marker sets (meta
data) about changesets through Mercurial? In particular I want to be
able to mark certain changesets as "bogus" if they lead to
regressions, store review comments and signatures on them as part of
the history and add various quality and post commit reports from
various builtbots and analysis tools.

2. is it possible to provide "alternative history" for patches that
are contained in Mercurial repository? By "alternative" I mean that if
changes to some directory are completely independent from any other
files, I'd like to create a history line from these patches that can
be viewed as independent and can be freely attached to any part of
repository history until there is a changeset that effectively
"anchors" the tree at some key revision (like when project is started
to be used, or at the appearance of new API symbol that is imported
from other files). Basically, the patch with "import independent" line
in some Python script is a changeset is anchored to revision at which
"independent" is functional, but Mercurial can not know it, so I'd
like to be able to map the dependency link between these two in the
history explicitly. It may result in completely different alternative
history DAGs with patches not connected to anything at all or even
having multiple tails (opposite of heads). Although I doubt Mercurial
supports alternative parent path for some changeset, or is it possible
to obsolete parents with ChangesetEvolution?
--
anatoly t.