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) |
(→Git for Linux Tools) |
||
| Line 1: | Line 1: | ||
= Git for Linux Tools = | = Git for Linux Tools = | ||
| − | In late February 2011, we moved from SVN to | + | 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 == | == First steps == | ||
Revision as of 11:36, 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