hash-obj | Get the hash of an object | Hashing library

I would say that you have logic issue in your code. According to the test scenario the fixture file_hashed must return a path to the existing file containing hash. One can see it here:

Today, git add and git commit are built into git and are not scripted. I think that git add was never scripted, but git commit certainly was. You can find the old implementation in contrib/examples of an old commit of the Git repository.

git commit was scripted around git write-tree and git commit-tree. git add is basically a glorified version of git update-index.

A clean way to get your proposed commits would be to make a new branch which removes file3 and then merge that.

As stated by the documentation (also refer to the -S and -G option to make sense of it) :
with this option, a commit will be mentioned if the number of occurrences of said object changes.

So, if you take the blobid of a file in your repo (say, the blobid of file Readme.md)

git log --find-object= will :

1. report commits where this blobid appears as file Readme.md (that's what you expect),
2. report commits where that blob disappears as file Readme.md, eg : a commit which changed the content of Readme.md from blobid to something else ;
3. report commits where this blob appears or disappears at some other path, eg : at some point, file doc/Doc.md contained had the exact same blobid ;
4. not report commits where a file with that exact content has been renamed, eg : file doc/Doc.md has been renamed to Readme.md, or from Readme.md to doc/Doc.md

You can run :

When writing a file to the database, the core.autocrlf tells git to run a filter on all input files to convert CRLF line endings to LF. It has to do this before calculating the hash of the blob, because every byte you change affects the hash, by definition.

Since git hash-object is the plumbing command used to do this, it too has to perform these filters. If you want to suppress that, and find the hash of the file if no filters were run, you can use the --no-filters option. Manual summary:

--no-filters

Hash the contents as is, ignoring any input filter that would have been chosen by the attributes mechanism, including the end-of-line conversion. If the file is read from standard input then this is always implied, unless the --path option is given.

Just to answer the original question, you can do that with a few low-level commands:

The problem is that on the one hand, QString ignores \0 as termination string, on the other hand, QByteArray always appends extra \0. From Qt's docs:

Using QByteArray is much more convenient than using const char *. Behind the scenes, it always ensures that the data is followed by a \0 terminator, and uses implicit sharing (copy-on-write) to reduce memory usage and avoid needless copying of data.

https://doc.qt.io/qt-5/qbytearray.html

So, every addData in your case is adding extra \0 to the data that is to be hashed. Some workaround might be the following code:

When you use echo -e, you're providing an octal escape when you write \0. Adding additional digits after that causes them to be interpreted as octal digits in the octal escape.

Since POSIX doesn't define echo -e and it isn't portable, it's better to use printf, since you know that the octal escape will be interpreted consistently and can contain at most three digits: