{"thread":{"id":"32705","subject":"Defensive publication on Git replication","startedAt":"2013-01-23T18:00:10Z","lastAt":"2013-01-23T18:00:10Z","messageCount":1,"participants":["Don Marti"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"207612","messageId":"4e91728c-ea52-448d-8174-f8487768a505@caret.perforce.com","threadId":"32705","inReplyTo":"a3951c54-efb8-476f-952f-4893bcc5e4a9@caret.perforce.com","subject":"Defensive publication on Git replication","fromName":"Don Marti","fromEmail":"dmarti@perforce.com","sentAt":"2013-01-23T18:00:10Z","receivedAt":"2013-01-23T18:00:10Z","isPatch":false,"sender":{"key":"dmarti@perforce.com","avatar":null},"body":"Just wanted to get this simple scheme out there in the hope of minimizing\npatent troll risks for people working on replication.\n\nYou run an update hook that blocks pushes unless the branch reference in\nthe repository matches the corresponding reference stored in a synchronized\nsystem, and flood the objects out using an inexpensive, simple system.\n\n(Apologies if this is too obvious for the list; I didn't want to take\nchances with the patent office definition of \"obvious.\")\n\n Replication Mechanism for a Distributed Version Control System \n http://ip.com/IPCOM/000225058\n\n Disclosed is a mechanism for replication of content repositories of a\n distributed version control system (DVCS), which is unique in that objects\n and branch references are transferred between nodes by independent means,\n with only branch references subject to synchronization among nodes. The\n object of this disclosure is to simplify deployment of a DVCS in a\n replicated configuration. Replication can be performed efficiently by\n transferring objects using a key-value store, such as a distributed hash\n table (DHT), independently of a repository's branch references, which are\n transferred using a synchronized data store.\n\n-- \nDon Marti           Perforce Software          +1-510-473-3142\nhttp://www.perforce.com/git-fusion\n"}]}