{"thread":{"id":"37635","subject":"What are git subtree push assertions?","startedAt":"2014-09-26T21:24:51Z","lastAt":"2014-09-26T21:24:51Z","messageCount":1,"participants":["Jorge Orpinel"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"249919","messageId":"CABf84+WFtO5rWHACk3cJagpKOnx2_USqWQ-vqtx+85fqEFbmzA@mail.gmail.com","threadId":"37635","inReplyTo":null,"subject":"What are git subtree push assertions?","fromName":"Jorge Orpinel","fromEmail":"jorge@orpinel.com","sentAt":"2014-09-26T21:24:51Z","receivedAt":"2014-09-26T21:24:51Z","isPatch":false,"sender":{"key":"jorge@orpinel.com","avatar":null},"body":"I asked this Q on\nhttp://stackoverflow.com/questions/26068474/what-are-git-subtree-push-assertions\n\nbut from previous experiences with git-subtree, people on\nstackoverflow (general public) don't really have complete answers so I\nresort to you!\n\n\n* What exactly are these assertions doing, and why does it have to\nstart from the beginning of the assertion count every time I subtree\npush?\n* Is there a way to limit the number of assertions? Something like git\nsubtree pull --squash perhaps. I don't want to wait this much or that\nit'll break at some point when there's just too many.\n\n\nPlease refer to link above for full question details. Thanks in\nadvance for any info you can give.\n\n\nJorge O.\n"}]}