On Evolve creating too many obsolete commits

[Pierre-Yves David]

On 05/02/2014 11:03 AM, Jordi Gutiérrez Hermoso wrote:
> On Fri, 2014-05-02 at 10:35 -0700, Pierre-Yves David wrote:
>>
>> On 05/02/2014 10:28 AM, Jordi Gutiérrez Hermoso wrote:
>>> About this section of the wiki (which has turned into an entirely
>>> tl;dr location of weirdly intermeshed rambling, and I'm trying to kill
>>> right now):
>>>
>>>       http://mercurial.selenic.com/wiki/EvolveUI#The_obsolete_history_is_not_very_usable
>>
>> Are you starting a discussion on a section which has not been
>> sanatasized//organized yet?
>
> Well, organising it is what I want to do. I'm asking how to do this.

As hinted at the beginning of the section:

   /!\ This section need some clarification /!\ consider using a 1. 
Example 2. explanation 3. possible actions format

You should be able to apply this before adding any new content

>>> The basic complaint is that since very history-editing operation
>>> creates obsolete commits, this is way too many obsoletes.
>>
>> I think the way to fix this topic is to improve:
>>
>> 1. tool to view obsolescence history (get me the obsolescence
>> history of X)
>
> This could be a revset, but...

deeply confused by your reply.

>> 2. have an easy way to annotate waypoint/state on this history (show me
>> the obsolescence history of this changeset, but only the point I marked
>> as relevant)
>
> This sounds like it needs a different UI than a simple CLI.

Even more deeply confuse by your reply. ☹


>>> My suggestion, then, is to have something like hg histedit --start
>>> mode where it saves the initial conditions, lets you do whatever you
>>> want to do DAG, and when you do hg histedit --finish, it only records
>>> the the final state as the replacements of the original state.
>>
>> And what happens to the intermediate one?
>
> I thought the intermediate ones could simply be stripped. The point of
> doing hg histedit --start is to say, "don't recode the intermediate
> states".

meh on stripping, but why not if it done well a fit with the way other 
multi step work. (but please focus on fixing the section firt)

>>> Can I kill this rambling section of the wiki with this suggestion?
>>
>> No, but you can augment it with your suggestion (along side of
>> cleaning it.)
>
> I'm wary of just outright deleting someone else's rambling without
> first getting permission to do it.

The request here is not about throwing away other people content, but 
about organising a wall of text into something worthwhile. Please makes 
it a priority before any further progress on this discussion.

-- 
Pierre-Yves