Skip to main content
Jump to: navigation, search

Difference between revisions of "Linux Tools Project/Git"

(Git for Linux Tools)
(First steps)
Line 3: Line 3:
  
 
== First steps ==
 
== First steps ==
* Learn about Git:  [http://progit.org/book/ Pro Git], [http://tom.preston-werner.com/2009/05/19/the-git-parable.html The Git Parable]
+
* Learn about Git:  [http://git-scm.com/ Git], [http://progit.org/book/ Pro Git], [http://tom.preston-werner.com/2009/05/19/the-git-parable.html The Git Parable], [http://library.edgecase.com/git_immersion/index.html Git Immersion]
 
* Read about [http://wiki.eclipse.org/Git Git at Eclipse]
 
* Read about [http://wiki.eclipse.org/Git Git at Eclipse]
 
* Note the [http://wiki.eclipse.org/images/7/78/Git-correct.png process] by which things must be committed at eclipse.org
 
* Note the [http://wiki.eclipse.org/images/7/78/Git-correct.png process] by which things must be committed at eclipse.org

Revision as of 10:37, 23 February 2011

Git for Linux Tools

In late February 2011, we moved from SVN to Git. Our SVN repositories were joined into one Git repository (and one for eclipse-build).

First steps

Commit messages

  • See guidelines others have written such as this one

Branches

  • Branches created for bug fixes
    • prefix the name with the bug # and a 'very' short description (ex. 307258-automake-tabs-to-spaces)
  • Release branches
    • stable-Major.Minor
  • Branches specific to a sub-project
    • namespaced (ex. valgrind/remote, lttng/super-awesome-feature)

Tags

Back to the top