"Ximin Luo" :

> For a start, there's the list of already-known issues.
<https://tests.reproducible-builds.org/index_issues.html>https
<https://tests.reproducible-builds.org/index_issues.html>://
<https://tests.reproducible-builds.org/index_issues.html>
tests.reproducible-builds.org
<https://tests.reproducible-builds.org/index_issues.html>/index_
<https://tests.reproducible-builds.org/index_issues.html>issues.html
<https://tests.reproducible-builds.org/index_issues.html> and I'd imagine
people analysing diffs would want an easy way to distinguish "issues that
someone else has already solved" vs "issues nobody has seen before".

Yes! I'm looking at those issues but it seems those issues are more in
number. Frankly speaking, I'm not completely aware about many of those.
Hence, I'm requesting you all to give some suggestions (and may be list of
issues) so that I can start working on it further.
Or maybe we can just categorize available issues :)

> Concretely I have some suggestions:
>
> 1. instead of calling this "ignore" we call it "hide". and instead of
"irrelevant" we say "common"/"minor"/"known"
>
> 2. diffoscope --ignore-* (or --hide-*) MUST NOT return 0 or otherwise
give the impression that two non-identical files are the same, even if all
differences are "hidden". It should report "n differences hidden".

I'm agree with this terminology :)

Thanks!
Satyam Zode
_______________________________________________
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Reply via email to