1 |
Dnia 2014-02-26, o godz. 07:39:51 |
2 |
Alex Xu <alex_y_xu@×××××.ca> napisał(a): |
3 |
|
4 |
> On 26/02/14 06:59 AM, Michał Górny wrote: |
5 |
> > Implementation-wise 'shallow' mode differs only when starting a new |
6 |
> > branch. In that case, '--depth 1' is used to avoid fetching earlier |
7 |
> > commits. Further updates are done through plain 'git fetch'. |
8 |
> |
9 |
> So this fetches all a..b commits. If the package hasn't been updated in |
10 |
> a while, wouldn't this be less efficient than a new clone? |
11 |
|
12 |
In a few rare cases, yes, that could happen. Though we can't really |
13 |
estimate or guess that :). |
14 |
|
15 |
If user suspects that, he can always remove the local repository |
16 |
and let the eclass re-fetch it. I doubt we can do more than that. |
17 |
|
18 |
-- |
19 |
Best regards, |
20 |
Michał Górny |