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