Michał Górny posted on Fri, 06 Sep 2013 14:27:17 +0200 as excerpted: > A shallow git clone is a clone of the repository which keeps only the > latest commit in the branch. Aside from many disadvantages and potential > issues, they are very popular as they allow our users to save both space > and bandwidth. Therefore, they are supported natively and used by > default in git-r3.
(Without reading thru all that source ATM...) What's the magic incantation for make.conf (or env/cat/pkg files) to force full repos, client side? I do enough git whatchanged checking and occasional bisection to make shallow clones something I don't want to even /think/ about. If I put the magic incantation in make.conf now, I won't have to worry about it when packages start switching over. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
