| 1 |
Dnia 2013-09-06, o godz. 16:55:41 |
| 2 |
Duncan <1i5t5.duncan@×××.net> napisał(a): |
| 3 |
|
| 4 |
> Michał Górny posted on Fri, 06 Sep 2013 14:27:17 +0200 as excerpted: |
| 5 |
> |
| 6 |
> > A shallow git clone is a clone of the repository which keeps only the |
| 7 |
> > latest commit in the branch. Aside from many disadvantages and potential |
| 8 |
> > issues, they are very popular as they allow our users to save both space |
| 9 |
> > and bandwidth. Therefore, they are supported natively and used by |
| 10 |
> > default in git-r3. |
| 11 |
> |
| 12 |
> (Without reading thru all that source ATM...) What's the magic |
| 13 |
> incantation for make.conf (or env/cat/pkg files) to force full repos, |
| 14 |
> client side? |
| 15 |
|
| 16 |
The eclass is fully documented, and therefore has a man page. |
| 17 |
And the mailing list is not your private support channel. Please learn |
| 18 |
to either: |
| 19 |
|
| 20 |
a) write on topic, |
| 21 |
|
| 22 |
b) create a new topic if you believe you have anything useful to say, |
| 23 |
|
| 24 |
c) ask on IRC, forums or even through private mail but *please* do not |
| 25 |
spam the mailing list. |
| 26 |
|
| 27 |
-- |
| 28 |
Best regards, |
| 29 |
Michał Górny |
Archives