[PATCH 2 of 3 highlight] test-highlight: expose bug in highlighting file with a formfeed

Augie Fackler raf at durin42.com
Wed Dec 17 10:16:55 CST 2014


On Dec 17, 2014, at 4:43 AM, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:

>> Why don't we document what's going on in that patch then?
>> 
>> (Genuinely confused here. )
> 
> So, my final goal is that if there is anything "strange" with that test (like, it disable a feature because the feature is broken in case X), I would like the test to explain that it test that Y in disable when X because Z is broken. And if Z because unbroken, the test can be dropped.
> 
> Even if the code disabling X is commented, having some data around the text will help someone in three year for now.
> 
> I that less confusing?

Mailed a v2, but forgot the v2 flag. You're cc'ed, so at least I got that part right.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20141217/ae127356/attachment.pgp>


More information about the Mercurial-devel mailing list