>From Phillip Susi, Mon 16 Mar 2020 at 14:32:46 (-0400) : > Instead of replacing the blob with an empty file, why not replace the > tree that references it with one that does not? That way you won't have > the file in your checkout at all, and the index won't list it so status > won't show it as changed. That's an interesting solution, but it only works if the tree itself does not change. - This is the case when these large objects were uploaded and then removed in another commit [*]. But in this case I won't checkout (usually) back to this tree anyway, so the error due to the missing blob is not a big problem. - When my coauthors use git as a dropbox alternative where they upload big pdf files (rather than only source code or .tex files), they also want to keep them there. If they had uploaded these files to the special literature/ folder I had made for them, I could just replace the literature/ tree by an empty one, but they managed to upload them in the root folder which is subject to change unfortunately, and it would be annoying to make a new replace ref each time. [*] by myself usually, for instance when people commit spurious tex generated files like eg *.synctex, despite my .gitignore (I don't know how they manage this...) -- Damien Robert http://www.normalesup.org/~robert/pro
