Liquid HG, (was: Sprint discussions/topics/outcome?)
Benoit Boissinot
bboissin at gmail.com
Sat Oct 16 17:07:20 UTC 2010
On Sat, Oct 16, 2010 at 6:41 PM, Augie Fackler <durin42 at gmail.com> wrote:
>
> On Oct 16, 2010, at 10:07 AM, Brendan Cully wrote:
>
>> On Saturday, 16 October 2010 at 16:51, Isaac Jurado wrote:
>>> Replying Nicolas Dumazet:
>>>>
>>>> Liquid HG is, in a sense, an unified abstraction on top of all
>>>> techniques that allow editing history. Once it is done, we will still
>>>> have multiple ways to modify history, but with a common vocabulary,
>>>> and commands in core to propagate "liquid" changes, as well as ways to
>>>> "freeze" liquid changes so that they're not editable again.
>>>
>>> Very nice, but the name has already been taken :-P
>>>
>>> http://bitbucket.org/bradobro/liquidhg/
>>>
>>> It's on Google Code too.
>>
>> How about "Mercurial Flux" or "HG Flux" ?
>
> I'm sure if we ask Brad will relinquish the liquidhg name - that was for investigation he was doing which became my year-long rewrite of httplib.
And anyway the liquidhg project is very different from what we call
liquid hg, there's no possible confusion.
Actually if it is implemented people won't refer to it as "liquid hg",
they will just say "this rev is liquid" and "that one is frozen". It's
more a UI/concept thing for end-users to understand the state of the
repo.
cheers,
Benoit
>
>> _______________________________________________
>> Mercurial-devel mailing list
>> Mercurial-devel at selenic.com
>> http://selenic.com/mailman/listinfo/mercurial-devel
>
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
>
More information about the Mercurial-devel
mailing list