| 1 |
Dnia 2014-09-16, o godz. 10:52:13 |
| 2 |
"W. Trevor King" <wking@×××××××.us> napisał(a): |
| 3 |
|
| 4 |
> $ git pull --depth=1 |
| 5 |
> |
| 6 |
> for subsequent syncs. pym/_emerge/actions.py currently hardcodes ‘git |
| 7 |
> pull’ for the latter, and doesn't seem to have any code for the |
| 8 |
> former. On the other hand, it wouldn't be too terrible to force users |
| 9 |
> to shallow their history manually whenever they felt like it. |
| 10 |
|
| 11 |
This isn't a good idea at all :). For git, --depth=1 fetching |
| 12 |
is the same thing as --depth=1 clone. This way, you refetch everything |
| 13 |
rather than just getting the update. |
| 14 |
|
| 15 |
Instead, plain 'pull' is more appropriate to just get the new objects. |
| 16 |
However, we may want to strip the history afterwards to reduce |
| 17 |
the clone size. |
| 18 |
|
| 19 |
-- |
| 20 |
Best regards, |
| 21 |
Michał Górny |
Archives