hg equivalent to "bk collapse"?

[Theodore Tso]

On Wed, Mar 14, 2007 at 12:57:57AM -0700, Mark Atwood wrote:
> With "bk collapse", you can do a lot of checkins into your local tree,
> which generate a lot of change history.  And then "collapse" them all
> together, for when you checkin to the upstream tree.  Thus everyone
> else doesn't have to see all your "nope, that didnt work either,
> trying something else" changelog entries.

What happens to the change history for the development checkins?  Do
they disappear, or do they get relegated to a branch that you just
don't push upstream, or do the development checkins just get marked as
"uninteresting" so they don't get displayed by default?  I could
imagine a number of different ways that this could be implemented, all
with different tradeoffs.

						- Ted