https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120554
--- Comment #11 from Sam James <sjames at gcc dot gnu.org> --- (In reply to David Binderman from comment #4) > (In reply to Sam James from comment #2) > > As jwakely explained before, you cannot use git blame and friends on a > > shallow clone. > > Oh dear, this again. > > It might be worth mentioning on page https://gcc.gnu.org/git.html > that the git history covers over 33 years and currently consumes about > 2.8 Gig of disk space. > You are free to use a large --depth= value if you really want, or a partial clone. > For folks on slow internet links, it takes quite some time to download. > Why are you downloading it repeatedly? Just run `git pull` every so often. git is designed to be efficient for small updates. > It looks to me like there is an opportunity for a git history > that only covers the last five years or so. Perhaps a split > into git-current and git-old would be a good idea ? No, git already lets you do that if you want to clone that locally, but seriously, just clone the whole thing and run `git pull` once a week or whatever. Can discuss more over mail if needed.
