Chris Lamb wrote:
> Looking forward to receiving your updated patch.
Paul, just wondering what your latest thoughts on this bug were? :) Is
this something you think you can drive or should someone take over..?
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'`
Hi Paul,
> EDID data is almost always proprietary so I'm not sure how to do that.
Something that at least has the first 'n' bytes or so so we can
check that the "recognition" for this file type works would be
the minimum here I think.
> > * expand that TODO item, I can't understand what it is
On Thu, 2018-04-26 at 09:08 +0200, Mattia Rizzolo wrote:
> * add a test
EDID data is almost always proprietary so I'm not sure how to do that.
> * expand that TODO item, I can't understand what it is about
diffoscope does not compare the output of the commands when one of them
returns an
Mattia Rizzolo wrote:
> First please:
> * add a test
> * expand that TODO item, I can't understand what it is about
> * wrap the long lines the way pep8 teaches
> * explain why the external_tools.py's dict lists both edid-decode and
>read-edid, but in the build-dep are made as
Package: diffoscope
Version: 93
Severity: wishlist
Tags: patch
I recently had occasion to compare two EDID files. I initially tried
diffoscope, saw only a hexdump and then manually compared the files
using a diff of pipes through edid-decode. Subsequently I looked up how
to add new formats to