Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Linux Tools Project/Git"
(→First steps) |
|||
| Line 3: | Line 3: | ||
== First steps == | == First steps == | ||
| − | * Read about [http://wiki.eclipse.org/Git | + | * Learn about Git: [http://progit.org/book/ Pro Git], [http://tom.preston-werner.com/2009/05/19/the-git-parable.html The Git Parable] |
| + | * 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 11:35, 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
- Learn about Git: Pro Git, The Git Parable
- Read about Git at Eclipse
- Note the process by which things must be committed at eclipse.org
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
- Tag each release with vMajor.Minor.Micro
- See Semantic Versioning for more details