From: Jakub Narebski <jnareb@gmail.com>
To: adam_kb <a-kyle@hotmail.com>
Cc: git@vger.kernel.org
Subject: Re: Fork or branch?
Date: Thu, 21 Apr 2011 07:38:08 -0700 (PDT) [thread overview]
Message-ID: <m3sjtbwu01.fsf@localhost.localdomain> (raw)
In-Reply-To: <1303390999618-6293910.post@n2.nabble.com>
adam_kb <a-kyle@hotmail.com> writes:
> I am new to git and understand most of it except for merge. My question is -
> if I have project X on branch master and its coded in python but I then want
> to take that same project and code it in say C or C++ would I fork or branch
> the project?
If you do not plan to merge your changes / your rewrite into project
X, then it is a fork (like e.g. LibreOffice.org is a fork of
OpenOffice.org).
Branch is in-repository line of development, e.g. 'stable' and
'unstable', or 'maint', 'master' and 'next' branches.
HTH
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2011-04-21 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 13:03 Fork or branch? adam_kb
2011-04-21 13:23 ` Peter Jönsson P
2011-04-21 14:38 ` Jakub Narebski [this message]
2011-04-21 18:33 ` Dmitry Potapov
2011-04-21 22:39 ` Jonathan Nieder
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=m3sjtbwu01.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=a-kyle@hotmail.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).