Sharing liquid history

[Isaac Jurado]

On Wed, Jan 19, 2011 at 11:52 PM, Pierre-Yves David
<pierre-yves.david at ens-lyon.org> wrote:
> First, Sorry for being a bit harsh and arrogant in the other mail. It's kind
> automatic, when anyone start talking about liquid, people get excited about all
> the cool stuff we can do with them and forget that still don't have the basic
> brick.

No problem.  I normally don't enter in design discussions because I
don't have enough knowledge of Mercurial's internals in order to make
useful contributions.  But in this particular case I had the
opportunity to explain an idea that has been hanging around my head
for some time.

>> Sorry to reply myself, but I forgot to ask how hard would it be to implement
>> liquid history with an overlay repository.
>
> The only way to gracefully handle concurrent modifications of liquid changes are
> to store a rich history of modifications made to them. The same we need vcs
> history to handle changes made to files. We need an history to handle changes made to
> changeset. The simplest way to do would be to store this liquid history into
> an overlay repository to add a nice UI to handle update and merge of concurrent
> modification.

I wasn't really meaning that.  Storing some kind of "meta-history" or
"transversal history" is something Matt is going to reject
automatically (remember the .hgtags discussions).