Difference between revisions of "Nice Version Control"

From FreekiWiki
Jump to navigation Jump to search
m
(→‎See Also: add moodle link)
Line 15: Line 15:
 
* [[CVS for coders]]
 
* [[CVS for coders]]
 
* [[Subversion for Coders]]
 
* [[Subversion for Coders]]
 +
* [http://lessons.freegeek.org/moodle/course/category.php?id=2 Moodle>>Coders, link to CVS 101]
  
 
[[Category:Coders]]
 
[[Category:Coders]]
 
[[Category:Distro]]
 
[[Category:Distro]]

Revision as of 03:58, 27 October 2005

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 freegeek: