# How to fork 2 messages from 2008-08-12 to 2008-08-12. Participants: Thomas Koch, Matthieu Moy. Thread: https://gitlist.dev/t/14951 ## Thomas Koch, 2008-08-12 08:30 Subject: How to fork Message-ID: <200808121030.21384.thomas@koch.ro> URL: https://gitlist.dev/e/200808121030.21384.thomas%40koch.ro ``` Hi, I just wonder, that neither the official Git manual, nor the kernel hackers guide to git describe the best practice to fork a project. My use case: There is an existing git repo git clone http://git.el-tramo.be/wigit.git which I want to fork. The original code should live in a separate branch in my local git repo (not master) so that I can still merge in changes. The result of my changes should be posted to my server. Could somebody be so kind to show me the list of commands which I'd need? Thanks a lot, -- Thomas Koch, Software Developer http://www.koch.ro Young Media Concepts GmbH Sonnenstr. 4 CH-8280 Kreuzlingen Switzerland Tel +41 (0)71 / 508 24 86 Fax +41 (0)71 / 560 53 89 Mobile +49 (0)170 / 753 89 16 Web www.ymc.ch ``` ## Matthieu Moy, 2008-08-12 09:09 Subject: Re: How to fork Message-ID: URL: https://gitlist.dev/e/vpqhc9q4n19.fsf%40bauges.imag.fr In-Reply-To: <200808121030.21384.thomas@koch.ro> ``` Thomas Koch writes: > I just wonder, that neither the official Git manual, nor the kernel > hackers guide to git describe the best practice to fork a project. Well, in Git, technically, any clone is a fork. The difference between a contributor's repository and a forker's is social, not technical (I usually define "fork" as a branch where one of the projects has no intention of merging the other's changes). So, just clone and publish (push) your changes, and you're done. Or, ask a more precise question, I may have missed something ;-). -- Matthieu ```