![]() If I use answer from above, then I get the diff between two hexdumps which is like concat-ing two hexdumps, so not very useful.Īs such, I've decided to patch git(v2.37.3 on Gentoo) to add -hexdump argument to git diff which works only in -binary mode, and now it looks like in this example: $ git diff -hexdump -binary HEAD~1 "./dated/sheet0005_older/2006/sheet0620/20000809_1118(3).JPG"ĭiff -git a/txt/papersheets/dated/sheet0005_older/2006/sheet0620/20000809_1118(3).JPG b/txt/papersheets/dated/sheet0005_older/2006/sheet0620/20000809_1118(3).JPG I liked answer above, however I wanted to see it in hexdump mode, rather than deflated(compressed) base85 "Git binary patch" format. See also for another example defining a hexdump diff command for use with image files. avoid any line ending conversions if using git on Windows), and also see any differences via hexdump: In my case I have several different file extensions which I want to treat as binary (e.g. gitattributes file should be checked into your repository. gitattributes file to tell git which files should be used with this special diff command: # Binary files (no line-ending conversions), diff using hexdump ![]() git/config file or your personal global $XDG_CONFIG_HOME/git/config/.gitconfig (usually $HOME/.gitconfig) file, for example a hex diff command using hexdump: ![]() You can define a new diff commands in your repository's. The answer from Roland Smith was helpful but is currently incomplete (see the comments) - there are two parts to this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |