Angelo Borsotti <angelo.borso...@gmail.com> writes: > When it executes the git pull it spends on my computer some 30 seconds, > obviously transferring the pdf file, that then it disregards because of the > merge=binary attribute. > When a commit contains many binary files, the command spends a lot of > time needlessly.
That is hardly needless nor useless. Unless you are saying that having a large pdf file as binary is useless in your history, that is. After such a merge or squash merge, you still need to be able to say "git checkout remote" to check out their version to inspect, and you did not have that version of the blob before that "git pull". -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
