Difference between revisions of "Nice Version Control"
m (good commit messages) |
m (add links to cvs/svn, and category:distro) |
||
Line 18: | Line 18: | ||
keep branches in sync, to make it easier to merge back into mainline | keep branches in sync, to make it easier to merge back into mainline | ||
+ | |||
+ | for more information about specific revision control systems at freegeek: | ||
+ | |||
+ | [[CVS_for_coders]] | ||
+ | [[Subversion_for_Coders]] | ||
[[Category:Coders]] | [[Category:Coders]] | ||
+ | [[Category:Distro]] |
Revision as of 15:11, 3 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
for more information about specific revision control systems at freegeek: