Difference between revisions of "Talk:1597: Git"
| Line 8: | Line 8: | ||
'Internally, Git works by saving the differences between various versions of the files, rather than creating a new copy each time the user "commits" the current version of the code.' - It is exactly the opposite. It stores whole files, or rather all committed pieces of data (blobs). See http://gitready.com/beginner/2009/02/17/how-git-stores-your-data.html [[Special:Contributions/141.101.88.202|141.101.88.202]] 09:38, 30 October 2015 (UTC)TK | 'Internally, Git works by saving the differences between various versions of the files, rather than creating a new copy each time the user "commits" the current version of the code.' - It is exactly the opposite. It stores whole files, or rather all committed pieces of data (blobs). See http://gitready.com/beginner/2009/02/17/how-git-stores-your-data.html [[Special:Contributions/141.101.88.202|141.101.88.202]] 09:38, 30 October 2015 (UTC)TK | ||
| − | + | : It is stored as diffs in pack file. Whole file (loose object) are packed automatically by default. | |
| − | + | : | |
| − | + | : See https://schacon.github.io/gitbook/7_the_packfile.html and https://www.kernel.org/pub/software/scm/git/docs/git-pack-objects.html [[Special:Contributions/162.158.177.59|162.158.177.59]] 10:15, 30 October 2015 (UTC) | |
Revision as of 11:06, 30 October 2015
If someone is interested, the best book I've read on it is Pro Git. The chapters 2 and 3 explain pretty well this mess of branching and merging. But it's true that it takes a bit of patience to go over it all. 108.162.228.35 08:47, 30 October 2015 (UTC)
Also take a look at GitFlow: A Successful Git Branching Model. Though Randall is correct there usually comes a time when it is easier to give up and "start again". 162.158.34.147 08:53, 30 October 2015 (UTC)
I never liked the name of this piece of software; in British English, the name "git" is mildly rude :-) https://en.wikipedia.org/wiki/Git_(slang) . Gearóid (talk) 09:20, 30 October 2015 (UTC)
'Internally, Git works by saving the differences between various versions of the files, rather than creating a new copy each time the user "commits" the current version of the code.' - It is exactly the opposite. It stores whole files, or rather all committed pieces of data (blobs). See http://gitready.com/beginner/2009/02/17/how-git-stores-your-data.html 141.101.88.202 09:38, 30 October 2015 (UTC)TK
- It is stored as diffs in pack file. Whole file (loose object) are packed automatically by default.
- See https://schacon.github.io/gitbook/7_the_packfile.html and https://www.kernel.org/pub/software/scm/git/docs/git-pack-objects.html 162.158.177.59 10:15, 30 October 2015 (UTC)
