{"thread":{"id":"44101","subject":"git-subtree pull issue","startedAt":"2016-09-16T22:39:36Z","lastAt":"2016-09-16T22:39:36Z","messageCount":1,"participants":["Alexander Inyukhin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"302083","messageId":"20160916223926.irf7q4ugjnwwmado@shurick.grid.su","threadId":"44101","inReplyTo":null,"subject":"git-subtree pull issue","fromName":"Alexander Inyukhin","fromEmail":"shurick@sectorb.msk.ru","sentAt":"2016-09-16T22:39:26Z","receivedAt":"2016-09-16T22:39:36Z","isPatch":false,"sender":{"key":"shurick@sectorb.msk.ru","avatar":null},"body":"When git-subtree is pulling data using the tag reference,\nit writes the tag's sha1 into a metadata.\nIt could be a problem next time, since this commit object\nis not a part of main tree, and could be lost.\n\nSteps to reproduce:\n\n# add some stuff to a existing tree\n# history will refer to v0.1 tag object instead of v0.1^{commit}\ngit subtree add --squash -P dir/ repo v0.1\n# prune all dangling objects including external v0.1 tag\ngit gc --aggressive --prune=all\n# this will fail\ngit subtree pull --squash -P dir/ repo v0.2\n"}]}