No subject

typical situation is when you have MQ patches applied and you pull
from somewhere else, a new head is created. =C2=A0Then you wan to pop all
patches, the process would be:

=C2=A0 =C2=A0- Copy the last pulled changesets into a bundle.
=C2=A0 =C2=A0- Truncate to trim all applied patches.
=C2=A0 =C2=A0- Re-apply bundled changesets.

Truncating and reapplying changesets can be dangerous, specially since
you cannot perform the two operations atomically (I think) and with
rollback support. =C2=A0Therefore, the ideal scenario would be to store
liquid changesets in completely separate, altough related, revlogs;
including the manifest and the changelog. =C2=A0That is why I think the
overlay repository is an interesting implementation for this:

http://mercurial.selenic.com/wiki/OverlayRepository

This way, mangling history is no longer potentially as dangerous as it
is now because you would only be allowed to mangle liquid history, and
it would be performed in a completely separate repository so frozen
history is not touched.

This is the only thing that worries me as a future user of this liquid
extension and that's why I wanted to enter the discussion.

Regards.

--=20
Isaac Jurado

"The noblest pleasure is the joy of understanding"
Leonardo da Vinci