Git development
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Thomas Koch <thomas@koch.ro>
Cc: git@vger.kernel.org
Subject: Re: How to fork
Date: Tue, 12 Aug 2008 11:09:54 +0200	[thread overview]
Message-ID: <vpqhc9q4n19.fsf@bauges.imag.fr> (raw)
In-Reply-To: <200808121030.21384.thomas@koch.ro> (Thomas Koch's message of "Tue\, 12 Aug 2008 10\:30\:21 +0200")

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

      reply	other threads:[~2008-08-12  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12  8:30 How to fork Thomas Koch
2008-08-12  9:09 ` Matthieu Moy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vpqhc9q4n19.fsf@bauges.imag.fr \
    --to=matthieu.moy@imag.fr \
    --cc=git@vger.kernel.org \
    --cc=thomas@koch.ro \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox