{"thread":{"id":"14951","subject":"How to fork","startedAt":"2008-08-12T08:30:21Z","lastAt":"2008-08-12T09:09:54Z","messageCount":2,"participants":["Thomas Koch","Matthieu Moy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"86909","messageId":"200808121030.21384.thomas@koch.ro","threadId":"14951","inReplyTo":null,"subject":"How to fork","fromName":"Thomas Koch","fromEmail":"thomas@koch.ro","sentAt":"2008-08-12T08:30:21Z","receivedAt":"2008-08-12T08:30:21Z","isPatch":false,"sender":{"key":"thomas@koch.ro","avatar":null},"body":"Hi,\n\nI just wonder, that neither the official Git manual, nor the kernel\nhackers guide to git describe the best practice to fork a project.\n\nMy use case: There is an existing git repo\n\ngit clone http://git.el-tramo.be/wigit.git\n\nwhich I want to fork. The original code should live in a separate branch\nin my local git repo (not master) so that I can still merge in changes.\n\nThe result of my changes should be posted to my server.\n\nCould somebody be so kind to show me the list of commands which I'd\nneed?\n\nThanks a lot,\n-- \nThomas Koch, Software Developer\nhttp://www.koch.ro\n\nYoung Media Concepts GmbH\nSonnenstr. 4\nCH-8280 Kreuzlingen\nSwitzerland\n\nTel    +41 (0)71 / 508 24 86\nFax    +41 (0)71 / 560 53 89\nMobile +49 (0)170 / 753 89 16\nWeb    www.ymc.ch\n"},{"id":"86917","messageId":"vpqhc9q4n19.fsf@bauges.imag.fr","threadId":"14951","inReplyTo":"200808121030.21384.thomas@koch.ro","subject":"Re: How to fork","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2008-08-12T09:09:54Z","receivedAt":"2008-08-12T09:09:54Z","isPatch":false,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"Thomas Koch <thomas@koch.ro> writes:\n\n> I just wonder, that neither the official Git manual, nor the kernel\n> hackers guide to git describe the best practice to fork a project.\n\nWell, in Git, technically, any clone is a fork. The difference between\na contributor's repository and a forker's is social, not technical (I\nusually define \"fork\" as a branch where one of the projects has no\nintention of merging the other's changes).\n\nSo, just clone and publish (push) your changes, and you're done.\n\nOr, ask a more precise question, I may have missed something ;-).\n\n-- \nMatthieu\n"}]}