On 31/10/2021 18:35, skybuck2000 wrote: > > You do know you get automatic de-duplication because filename > metadata > is stored independently of content (blobs), so copied file > contents take > up zero room! > > > I am in doubt what this means. I take the blog theory of GIT with a > grain of salt. I have seen it fail to detect blobs.
Blobs _are_ simply file contents (as stream of bytes). The blob's name is the hash of that stream. If the stream is the same, then it has the same name (hash) and references the existing 'copy' (e.g. all the identical GPL2 licence files!) > > > > > 5b remote branches > > Mental mind trap: these are held locally when fetched. You can > reference > them _instantly_ and start a new work-branch directly from them, > without > having to create a 'local' version first > > > Yes this I understand that they are locally fetched. This is the cool > thing, it feels like they are remotes, but they are stored on my drive > and I can see and work on/copy from them at any time and if/when it > pleases me I could even upload something if it's not to old and then > it may sync-up or issue a pull request on their remotes which is very > cool, lots of automation there... > Because the remotes will have a lot of common parts (early history) they take zero space, because of hash deduplication. its only the new bits that take any space, and mainly it's small "deltas" within the pack files. Philip -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/c1344a85-24ce-9e92-b1fb-5fe5aaf3ff49%40iee.email.
