md5sums of files
In my experience, if you're on a very lossy network connection (e.g. wifi at a hackathon where there's 100+ ppl), git pull on lfs can easily be dropped. Here are the md5sums for commit 5d853ed7d16ac794afa8f5c9c7f59f4e9c950954 :
tokenizer_config.json: 53cf4cf12df1da52a733f02170292cbd
model.safetensors: 1dfb5121d35c822fd07102ccddd0fbc8
generation_config.json: 7d7587e6ac5bb8723fa558d66bd0c7da
USE_POLICY.md: 1729addd533ca7a6e956e3f077f4a4e9
tokenizer.json: 3ff6b653d22a2676f3a03bd7b5d7ff88
README.md: 32bb7c728ace9ee2899596376da653c4
special_tokens_map.json: 4b3afa18fffa4e1e60e3de9cc83a6dab
config.json: 0c3a876411f4825b689987922800497c
LICENSE.txt: d665b7f3a12a6b763c45af10708c4e67
.gitattributes: a859f8a89685747ffd4171b870540c41
original/consolidated.00.pth: e8cc8b0ff8d1f588c8e747840c569ea1
original/tokenizer.model: 08292403f8b173e7524d7fba7bbbd2d3
original/params.json: ea525bcaf082df3020dadc7bcc6451a1
should the md5sums of the files in .git of the local git repository copy matter?
Nevertheless, maybe we could "normalize" providing md5sums! (I'll take sha256sum as well)