threads / discuss / 14951

How to fork

Subject: How to fork

## tl;dr

2 messages between Aug 12, 2008 and Aug 12, 2008.

replies: 1people: 2as markdown or json

Thomas Koch· Aug 12, 2008, 08:30 UTC · lore

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· Aug 12, 2008, 09:09 UTC · re: Thomas Koch · lore

Re: How to fork

Thomas Koch <thomas@koch.ro> 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