D6356: mdiff: prepare mdiff to be used for run-tests to replace unidiff

martinvonz (Martin von Zweigbergk) phabricator at mercurial-scm.org
Fri May 10 13:44:24 EDT 2019

martinvonz added a comment.

  In https://phab.mercurial-scm.org/D6356#92453, @sangeet259 wrote:
  > In https://phab.mercurial-scm.org/D6356#92451, @martinvonz wrote:
  > > > The future changes to run-tests.py will enable one to use mdiif
  > > >  to diff rather than unidiff whenever the mercurial is installed in the system.
  > >
  > > Perhaps a naive question, but why is that desirable? How will I (as someone running tests) notice?
  > @martinvonz 
  >  This patch is a breakdown of the earlier patch https://phab.mercurial-scm.org/D5514
  Oh, nice! I sometimes use `run-tests.py -i` and just accept an unreadable diff because I know that `hg diff` might make it easier to read. I had not understood why :)
  > There <https://phab.mercurial-scm.org/D5514> I have detailed why is this required.
  >  In short, the diff output of tests is a bit ugly compared to what hg diff does, which is much nicer.
  > I am thinking of putting that descriptive commit message in the patch 2/2.
  Perhaps also adding a "which gives simpler diffs" or something like that to this patch?

  rHG Mercurial


To: sangeet259, #hg-reviewers
Cc: martinvonz, mercurial-devel

More information about the Mercurial-devel mailing list