Date: Thu, 14 Mar 2019 23:07:05 -0400 From: Ed Maste <emaste@freebsd.org> To: "Rodney W. Grimes" <rgrimes@freebsd.org> Cc: src-committers <src-committers@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, svn-src-head <svn-src-head@freebsd.org> Subject: Re: svn commit: r345138 - head/share/man/man9 Message-ID: <CAPyFy2Caxx-MSRqFruV%2Bq-A9LJbzP-okJvWLAmQaLKgOW8uQnQ@mail.gmail.com> In-Reply-To: <201903150239.x2F2dH9m028042@gndrsh.dnsmgr.net> References: <CAPyFy2B09hOx=tSNOMSCyhW9SdP_5ySfOuTFQZvZutfhgTi2bg@mail.gmail.com> <201903150239.x2F2dH9m028042@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 14 Mar 2019 at 22:39, Rodney W. Grimes <freebsd@gndrsh.dnsmgr.net> wrote: > > 4. There is no easy way to show > "changed byte at offset 0x432 from 0xef to 0xfe" But this is not that easy with uuencoded files, either - I'd just end up uudecoding both files before running cmp -x. And for the case under discussion here (firmware files) we treat them as opaque binary objects; comparing them is generally not interesting anyway. > Do we have a decent binary diff and binary patch tool? We have bsdiff and bspatch, but their output is not designed for human consumption or editing.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2Caxx-MSRqFruV%2Bq-A9LJbzP-okJvWLAmQaLKgOW8uQnQ>