application icongmusicbrowser

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Last revisionBoth sides next revision
guide:git [2010/01/20 02:15] – created squentinguide:git [2013/04/23 17:31] – update sourceforge git url squentin
Line 2: Line 2:
 [[http://en.wikipedia.org/wiki/Git_%28software%29|Git]] is a distributed revision control, that you can use to keep up to date to the latest modification in gmusicbrowser. [[http://en.wikipedia.org/wiki/Git_%28software%29|Git]] is a distributed revision control, that you can use to keep up to date to the latest modification in gmusicbrowser.
 And as gmusicbrowser doesn't need compilation (apart from translations), git makes it very easy to follow gmusicbrowser development. And as gmusicbrowser doesn't need compilation (apart from translations), git makes it very easy to follow gmusicbrowser development.
 +
 +gmusicbrowser git repositories :
 +  * github : http://github.com/squentin/gmusicbrowser
 +  * sourceforge : https://sourceforge.net/p/gmusicbrowser/code/ci/master/tree/
 +
 +this link will download a snapshot of the latest version : http://github.com/squentin/gmusicbrowser/tarball/master
 +
 +The repository contains 2 branches :
 +  * master : the default branch, that currently contains v1.1.x
 +  * v1.0.x
  
 This mini-guide will show you some basic commands that you will need to follow gmusicbrowser development with git, visit the [[http://git-scm.com/documentation|official site]] for more information. This mini-guide will show you some basic commands that you will need to follow gmusicbrowser development with git, visit the [[http://git-scm.com/documentation|official site]] for more information.
Line 49: Line 59:
 To create/update the translations files in gmusicbrowser/locale/, you'll need to do : To create/update the translations files in gmusicbrowser/locale/, you'll need to do :
 <code>make locale</code> <code>make locale</code>
 +//note that this requires the gettext package//
 +
 As this modifies po/*.po you'll need to follow with a As this modifies po/*.po you'll need to follow with a
-<code>git reset --hard</code>+<code>git checkout po/*.po</code> 
 +To revert the changes to po/*.po files, else git won't let you update the branch or change branch (to prevent the loss of these modifications). 
 + 
 +===== tips ===== 
 +The "git status" command can be helpful to know the current status : current branch, which tracked files are modified ... 
 + 
 +An even better way is to use a command prompt that indicates the current branch, if there are untracked/staged changes, and more.
  
 ===== Making local changes ===== ===== Making local changes =====
Line 60: Line 78:
 git rebase master git rebase master
 </code> </code>
-if there are conflicts, you can resolve them manually or use +if there are conflicts, you can resolve them manually or use "''git rebase --abort''" to abort the rebase. 
-git rebase --abort +Do not use rebase on branch you published, as rebase rewrite the history of the branch, use merge instead. 
-to abort the rebase.+ 
 +===== Cloning branches from other repository ===== 
 +You can easily track branches from other repository, for example, to track ochosi's branch : 
 +<code> 
 +git remote add ochosi git://github.com/ochosi/gmusicbrowser.git 
 +git fetch ochosi 
 +git checkout -b ochosi ochosi/master 
 +</code> 
 +The first line creates a new remote named "ochosi" (you can list the remotes with "git remote"
 + 
 +The second line fetches the remote's data, and create the remote branches, here ochosi/master (you can view it with "git branch -a")
  
 +the third creates a local branch "ochosi" that tracks the remote branch "ochosi/master"
guide/git.txt · Last modified: 2022/05/23 01:30 by 127.0.0.1
CC Attribution-Share Alike 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0