Hi there, I've posted a git repository to the web that is an rsync copy of my development archive's .git directory, with update-server-info run on it. Now if I understand correctly, this contains a single file for every commit/file/whatever else I ever made, which is a paint over HTTP. I have then recently learned about the wonder that is git repack, which I would love to use on this repository, were it not for this comment in its manpage: 8< ---------------------------------------------------------------------- Especially useful when packing a repository that is used for private development and there is no need to worry about people fetching via dumb protocols from it. 8< ---------------------------------------------------------------------- It says this relating to the '-a' option, but it makes me wonder if I'll break copies of the repo that other people have pulled if I use 'repack'? What are the possible interactions and things to keep in mind between repack and dumb protocols? In any case, I would like to suggest that the rather ominous-sounding text in the manpage be replaced with something more concrete, i.e. "If you repack an archive that has people fetching via dumb protocols from it, X, Y, and Z will happen." Thanks, Andreas (please cc--not subscribed)
Attachment:
signature.asc
Description: This is a digitally signed message part.