Help designing the evolve UI
Didly
didlybom at gmail.com
Thu Apr 24 22:54:42 UTC 2014
On Thu, Apr 24, 2014 at 3:51 AM, Pierre-Yves David
<pierre-yves.david at ens-lyon.org> wrote:
>
>
> On 04/18/2014 01:56 AM, Aurélien Campéas wrote:
>>
>> On 18/04/2014 00:05, Jordi Gutiérrez Hermoso wrote:
>>>
>>> >On Thu, 2014-04-17 at 16:50 +0200, Aurélien Campéas wrote:
>>> >
>>>>
>>>> >>Stripping obsolescence markers is useful for the same reason strip
>>>> >>is useful (and to be used wisely & sparingly).
>>>> >>
>>>> >>Now, if there are theoretical or practical objections to that,
>>>> >>I'd like to know them. I'm not, however, interested in anathems.
>>>
>>> >
>>> >The problem is that stripping obsolescence markers is really the exact
>>> >same situation as stripping csets: you have to do it locally and then
>>> >check if you have to do it in any remote repo. Then you're in the same
>>> >situation we have now with stripping.
>
>>
>>
>> Yes. This is assumed. I gave a reasonnable use case. These things
>> do happen.
>
>
> This wiki page: http://mercurial.selenic.com/wiki/EvolveUI should be the
> vessel of reasonable use case. Can you please adds your there?
>
> --
> Pierre-Yves David
I added some stuff to the pain points section.
Cheers,
Angel
More information about the Mercurial-devel
mailing list