LiquidHg via MQ

[Arne Babenhauserheide]

On Tuesday 03 May 2011 10:37:45 Kevin Bullock wrote:
> On May 2, 2011, at 7:56 PM, Arne Babenhauserheide wrote:
> > This might be a naive question, but could LiquidHg be implemented as an
> > interface to versioned MQ?
> 
> That's sort of backwards to the point of LiquidHg; it's meant to provide a
> unified way for all the history-editing mechanisms to be able to work
> safely. Thus MQ should (eventually) be built on top of LiquidHg, not the
> other way round.

It’s an implementation question, not a concept question. 

If the interface of LiquidHG can be realized with MQ as backend, it is 
possible to realize it without having to reimplement all of the functions of 
MQ. 

I see a specific shortcoming, though: MQ does not have a full history tree/DAG 
for patches with potentially branchy ancestor information → That’s the 
weakness I was searching for: The reason why LiquidHG is the more general 
system.

> > PS: Is it really necessary to add garbage collection when using
> > bookmarks? That violates the principle that no work gets lost without
> > explicit action by replicating a (mis-)feature of git.
> 
> That doesn't seem to be a part of the current thinking (and I hope the idea
> has actually died, because it would basically kill the simple workflow).

How would it kill the simple workflow to require explicit action to destroy 
changesets not referenced by a bookmark? It’s not like gc is needed in normal 
operation, as it is for git (because git creates quite much garbage).

> The changesets remain in
> existing clones and can be _manually_ pulled into new ones.

That sounds nicer than garbage collection :)

> Nope, the notes say pretty clearly that with some manual intervention,
> you'll be able to liquefy existing changesets. That's pretty much morally
> equivalent to history editing, though.

It wasn’t clear for me from the notes, that’s why I asked. Thanks for 
clarifying.

Best wishes, 
Arne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20110503/76b8f6b5/attachment.asc>