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"
(Initial revision) |
(Add some formatting) |
||
| Line 1: | Line 1: | ||
| − | First steps | + | = 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 == | ||
* 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 == | ||
* Branches created for bug fixes | * Branches created for bug fixes | ||
** prefix the name with the bug # and a 'very' short description (ex. 307258-automake-tabs-to-spaces) | ** prefix the name with the bug # and a 'very' short description (ex. 307258-automake-tabs-to-spaces) | ||
| Line 14: | Line 19: | ||
** 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 | ||
Revision as of 11:23, 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
- 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