git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to fork

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Aug 12, 2008, 09:09 UTC
Message-ID
<vpqhc9q4n19.fsf@bauges.imag.fr>
In-Reply-To
<200808121030.21384.thomas@koch.ro>
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
Previous: Thomas Koch
Message 2 of 2 in “How to fork”
  1. Thomas KochAug 12, 2008
  2. Matthieu MoyAug 12, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.