| 1 |
On Sun, 24 Jan 2016 11:38:42 -0500 |
| 2 |
Göktürk Yüksek <gokturk@××××××××××.edu> wrote: |
| 3 |
|
| 4 |
> > "Again you should not compress these patches because git does not |
| 5 |
> > play well binary files". |
| 6 |
> > |
| 7 |
> > I'm not sure this statement still holds true with git. Does it? |
| 8 |
> > |
| 9 |
> It should be possible to compress the patches and use gitattributes[1] |
| 10 |
> to tell git to decompress them before diffing. But doing so is not |
| 11 |
> needed since git compresses its objects in the first place. Maybe we |
| 12 |
> can rewrite this as "You should not compress these patches because git |
| 13 |
> compresses them upon commit transparently." |
| 14 |
|
| 15 |
I think that's beside the point. Regular users fetch the tree with |
| 16 |
rsync, not git, and the limit is primarily there to avoid bloating that |
| 17 |
transfer. |
| 18 |
|
| 19 |
-- |
| 20 |
James Le Cuirot (chewi) |
| 21 |
Gentoo Linux Developer |
Archives