{"thread":{"id":"32654","subject":"Re: Question re. git remote repository","startedAt":"2013-01-17T05:20:07Z","lastAt":"2013-01-17T05:20:07Z","messageCount":1,"participants":["Matt Seitz"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"207136","messageId":"1BBEF94B6B46E54980290D150A6F2EDD46B718CB@BLUPRD0612MB625.namprd06.prod.outlook.com","threadId":"32654","inReplyTo":null,"subject":"Re: Question re. git remote repository","fromName":"Matt Seitz","fromEmail":"mseitz@mhseitz.onmicrosoft.com","sentAt":"2013-01-17T05:20:07Z","receivedAt":"2013-01-17T05:20:07Z","isPatch":false,"sender":{"key":"mseitz@mhseitz.onmicrosoft.com","avatar":null},"body":"\"David Lang\" <david@lang.hm> wrote in message news:<alpine.DEB.2.02.1301161843390.21503@nftneq.ynat.uz>...\n> >>\n> >> On Thu, 17 Jan 2013, Matt Seitz (matseitz) wrote:\n> >>\n> >>> 2. a repository where only one user does \"git add\" and \"git commit\",\n> >> while other users will do \"git pull\", the peer-to-peer model (you pull changes\n> >> from me, I pull changes from you).\n> >>\n> \n> you may _be_ safe, and if others who really know the internals speak up, take \n> their word on it. \n\nWell, we already have Linus's article.  I guess the question is whether the use case I describe above falls under:\n\nA. \"maintenance operations\"\n\nB. \"normal git workflow\"\n\nPersonally, I would consider this use case to be a \"normal git workflow\".\n"}]}