[Commented On] D10915: upgrade_utils: add support for enabling internal phases during upgrade

[marmoute (Pierre-Yves David)]

marmoute added a comment.


  In D10915#166896 <https://phab.mercurial-scm.org/D10915#166896>, @Mathiasdm wrote:
  
  > It sounded to me like 'hg prune' and 'hg strip --soft' both covered the same use case.
  > The main benefit to me seemed that 'hg strip --soft' doesn't require me to enable evolve for all our users.
  
  What are you trying to achive with `hg strip --soft` that you cannot achieve with evolve. And what are the things blokcing you from enabling evolution for all your users ?
  
  > I would like to have obsolescence markers for all our users, but without a properly working 'hg strip', that wasn't possible.
  
  `hg strip` is properly working. It is doing exactly what it is documented to do :-)
  
  `hg strip --soft` with evolution -is- not properly working as it is going to hide content, without hiding the associated obsmarkers, leading to indecipherable situation for users. So mixing the two is not the way to go (and one of the reason the feature is still experimental).

REPOSITORY
  rHG Mercurial

CHANGES SINCE LAST ACTION
  https://phab.mercurial-scm.org/D10915/new/

REVISION DETAIL
  https://phab.mercurial-scm.org/D10915

To: Mathiasdm, #hg-reviewers
Cc: marmoute, mercurial-patches
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-patches/attachments/20210628/0b838d23/attachment-0002.html>