Difference between revisions of "Nice Version Control"
Jump to navigation
Jump to search
(actual content) |
(→See Also: link to "git for dummies") |
||
| (7 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | Very basic and generic guidelines for working with others using a revision control system: | |
| − | control system: | ||
| − | + | * Update your working copy before modifying anything | |
| + | * Always diff before you commit, to avoid committing anything unintentionally | ||
| + | * Write accurate, meaningful and ideally concise commit messages. | ||
| + | * Commit smaller, logically grouped changes together | ||
| + | ** (This makes it easier to revert a specific change without reverting unrelated stuff, too.) | ||
| + | * Avoid conflicts when possible by knowing who's working on what parts | ||
| + | * When implementing major changes, check in with others working on the project | ||
| + | * Try to implement major changes in a branch first | ||
| + | * Keep branches in sync, to make it easier to merge back into mainline | ||
| − | + | == See Also == | |
| − | + | For more information about specific revision control systems at Free Geek: | |
| − | + | * [[Subversion for Coders]] | |
| − | + | * [[Git for dummies]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:Coders]] | [[Category:Coders]] | ||
| + | [[Category:Distro]] | ||
Latest revision as of 01:39, 17 November 2008
Very basic and generic guidelines for working with others using a revision control system:
- Update your working copy before modifying anything
- Always diff before you commit, to avoid committing anything unintentionally
- Write accurate, meaningful and ideally concise commit messages.
- Commit smaller, logically grouped changes together
- (This makes it easier to revert a specific change without reverting unrelated stuff, too.)
- Avoid conflicts when possible by knowing who's working on what parts
- When implementing major changes, check in with others working on the project
- Try to implement major changes in a branch first
- Keep branches in sync, to make it easier to merge back into mainline
See Also
For more information about specific revision control systems at Free Geek: