Skip to main content
Jump to: navigation, search

Difference between revisions of "Linux Tools Project/Git"

(Tags)
Line 5: Line 5:
 
* 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
 
  
 
== Commit messages ==
 
== Commit messages ==
 
* See guidelines others have written such as [http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html this one]
 
* See guidelines others have written such as [http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html this one]
 
  
 
== Branches ==
 
== Branches ==
Line 18: Line 16:
 
* Branches specific to a sub-project
 
* Branches specific to a sub-project
 
** namespaced (ex. valgrind/remote, lttng/super-awesome-feature)
 
** namespaced (ex. valgrind/remote, lttng/super-awesome-feature)
 
  
 
== Tags ==
 
== Tags ==
 
* Tag each release with vMajor.Minor.Micro
 
* Tag each release with vMajor.Minor.Micro
 
* See [http://semver.org/ Semantic Versioning] for more details
 
* See [http://semver.org/ Semantic Versioning] for more details

Revision as of 10:25, 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