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

Re: Really beginner on Version Control

From
Thomas Moulard <thomas.moulard@gmail.com>
Date
Sep 21, 2010, 14:59 UTC
Message-ID
<AANLkTimm=x37EiyGObfJ_gdU6OtGbdCCOEw0XjVDH_oQ@mail.gmail.com>
In-Reply-To
<1285080133451-5555023.post@n2.nabble.com>
Hi!

On Tue, Sep 21, 2010 at 4:42 PM, FernandoBasso <FernandoBasso.br@gmail.com> wrote:

Show 5 quoted lines
>
> 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 ?

Ususally, one develops a feature on a separate branch to avoid polluting the "master" branch with non working or fragile commits and prevent other people from working.

You always merge a branch into the branch you *are* in. For instance: # Switch to master branch. $ git checkout master

# List the available branches.
$ git branch
* master
  my-new-feature

# Merge the topic branch into master. $ git merge my-new-feature

Here what I call a topic branch is what you call a "testing" branch.
>
> 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
> ?

If there is a conflict, in theory it means that *both* sides have change a same location in a tracked file. Usually, it means that you have to take *both* contents and depending on the context write manually the result.

For instance, one can fork master to create a topic branch, then changes are made in the topic branch and in master. When you merge back your topic branch you want to integrate your changes but also preserving the changes that have been made to master between the time the topic branch has been created and now.

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

In general, yes. Please note that git can work around whitespace problems (whitespace versus tab and \n versus \r\n).

You may also want to google "git workflow" to get a rough idea about how to manage a project with git and how to do more advanced stuff with topic branches.

I hope it helps,
-- 
Thomas Moulard
Previous: FernandoBassoNext: Enrico Weigelt
Message 2 of 17 in “Really beginner on Version Control”
  1. FernandoBassoSep 21, 2010
  2. Thomas MoulardSep 21, 2010
  3. Enrico WeigeltSep 21, 2010
  4. Eric RaibleSep 24, 2010
  5. Enrico WeigeltSep 24, 2010
  6. FernandoBassoSep 24, 2010
  7. Andreas EricssonSep 21, 2010
  8. Jakub NarebskiSep 21, 2010
  9. FernandoBassoSep 22, 2010
  10. Andrew KellerSep 22, 2010
  11. FernandoBassoSep 22, 2010
  12. FernandoBassoSep 22, 2010
  13. Tor ArntsenSep 22, 2010
  14. Dmitry PotapovSep 22, 2010
  15. Thomas HochsteinSep 22, 2010
  16. Dmitry PotapovSep 22, 2010
  17. Dmitry PotapovSep 22, 2010

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.