Help designing the evolve UI

[Martin Geisler]

Pierre-Yves David <pierre-yves.david at ens-lyon.org> writes:

> On 04/23/2014 01:02 AM, Martin Geisler wrote:
>> I described an example where I thought the step-by-step evolving would
>> be interesting:
>>
>>    http://mercurial.markmail.org/message/5kctrmri5cqjxclo
>>
>> It didn't feel very useful or powerful to me -- I basically had no idea
>> if I wanted to run 'hg evolve' or 'hg evolve --any' or if I should have
>> updated to another commit before running the two commands.
>>
>> In other words: the steps needed to bring a repository back to an
>> untroubled state are completely opaque to me.
>
> I looks like you got valuable material here.
>
> However, if you are trying to revive this thread instead of updating
> the wiki, "you are doing it wrong"¹.
>
> Please update the wiki page under either a "Use case" or "Pain Point"
> (pick what suit the best)

Thanks for the hint :) I've updated the wiki:

  http://mercurial.selenic.com/wiki/EvolveUI#Evolve_Steps_can_be_Opaque

-- 
Martin Geisler
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20140423/e76d971b/attachment.pgp>