Jun Wu <qu...@fb.com> writes:
> Could we consider storing the topic of a changeset elsewhere so it's not
> part of the changeset metadata? This will make it more lightweight and
> help preserve hashes with remote peers.
I assume this is along the spirit of your 'hg undo' for evolve (that
preserves the hash)?
One of the nice features of the topic name being in the hash is that a
server (Bitbucket in this case) can enforce settings with bundle1 since
we can't really control the client of our users (unlike Facebook and
Mercurial-devel mailing list