git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: FernandoBasso <FernandoBasso.br@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Really beginner on Version Control
Date: Tue, 21 Sep 2010 18:40:23 +0200	[thread overview]
Message-ID: <4C98DFF7.2030801@op5.se> (raw)
In-Reply-To: <1285080133451-5555023.post@n2.nabble.com>

On 09/21/2010 04:42 PM, FernandoBasso wrote:
> 
> I am really a beginner in. Bear with me please.
> 
> Why do we merge, say a testing branch into the master branch ? What is the
> use of it ?
> 

Because the sum of the whole is greater than the parts. Most features in git
for example are developed on topic branches. This makes it possible to keep
unfinished code separate from the production branch that people actually use.

> When there is a conflict when merging branches (merging the testing into the
> current branch), should I edit the 'current' branch or the 'testing' branch
> ?
> 

You should edit the working tree, since that's where the conflict will be
staged. When you're done, commit the results and that will be a new commit
on the branch you're on.

> Should both branches have exactly the same code so that they can be merged
> without conflicts ?
> 

Both branches should most definitely not have exactly the same code. If they
did, there would be no point in merging them. The merge-result shouldn't
have the same code as any of the branches either, unless you actually want
to throw one branch away, in which case you'd be far better off doing just
that.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

  parent reply	other threads:[~2010-09-21 16:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 14:42 Really beginner on Version Control FernandoBasso
2010-09-21 14:59 ` Thomas Moulard
2010-09-21 14:59 ` Enrico Weigelt
2010-09-24 19:33   ` Eric Raible
2010-09-24 20:18     ` Enrico Weigelt
2010-09-24 21:25     ` FernandoBasso
2010-09-21 16:40 ` Andreas Ericsson [this message]
2010-09-21 23:35 ` Jakub Narebski
2010-09-22  0:13   ` FernandoBasso
2010-09-22  3:52     ` Andrew Keller
2010-09-22 11:45       ` FernandoBasso
2010-09-22 11:49         ` FernandoBasso
2010-09-22 12:50           ` Tor Arntsen
2010-09-22 22:15         ` Dmitry Potapov
2010-09-22  7:31     ` Thomas Hochstein
2010-09-22 22:13     ` Dmitry Potapov
2010-09-22 22:10 ` Dmitry Potapov

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=4C98DFF7.2030801@op5.se \
    --to=ae@op5.se \
    --cc=FernandoBasso.br@gmail.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).