| 1 |
On 26 June 2011 15:49, Wyatt Epp <wyatt.epp@×××××.com> wrote: |
| 2 |
> As for the latter part, the size of a git repo becoming umanageable |
| 3 |
> over time had not occurred to me, I'm afraid-- would it work to use |
| 4 |
> shallow clones? Otherwise, the herd-wise division is probably |
| 5 |
> acceptable. Need to think about that one more. |
| 6 |
|
| 7 |
|
| 8 |
--depth <depth> |
| 9 |
Create a shallow clone with a history truncated to the specified |
| 10 |
number of revisions. A shallow repository has a number of |
| 11 |
limitations (you cannot clone or fetch from it, nor push from nor |
| 12 |
into it), but is adequate if you are only interested in the recent |
| 13 |
history of a large project with a long history, and would want to |
| 14 |
send in fixes as patches. |
| 15 |
|
| 16 |
It would be ok perhaps for non-contributing users to use shallow |
| 17 |
clones, but in my understanding, shallow clones limit you to doing |
| 18 |
what you could do with a tar file of the specified revision, which |
| 19 |
basically makes it impractical for people who are developing on it, |
| 20 |
and would mean every new developer would get a progressively longer |
| 21 |
time in order to do a complete check out. |
| 22 |
|
| 23 |
( Unless of course we had some sort of periodic refresh where history |
| 24 |
was discarded/rebased into nonexistence , but that is really the same |
| 25 |
problem with different faces ) |
| 26 |
|
| 27 |
-- |
| 28 |
Kent |
| 29 |
|
| 30 |
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, |
| 31 |
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );" |
| 32 |
|
| 33 |
http://kent-fredric.fox.geek.nz |
Archives