Changes by last author:
Changed:
| CVS is a wonderful collaboration and version-tracking tool, you can benefit a lot from learning how to use it, it's not that complicated. |
|
CVS and SVN are wonderful collaboration and version-tracking tools
If you were suggested to get firmware from CVS, you are lucky: We use the released firmware version that can be simply downloaded from GenBoard/UnderDevelopment/FirmwareChanges (instead of CVS). It is generated from SVN repository https://svn.x-dsl.hu/svn/firmware/firmware/branches/stable1_0 Note that firmware is NOT maintained in CVS any longer but SVN ! Subversion (== SVN) is an improved version tracking system similar to CVS (user commands are mostly compatible with CVS). See SubVersionSvn and [SVN book]. ---- Version tracking tools makes your life nicer if you: * work on a set of files (sourcecode, webpage, CAD-files, etc...) on more than one computer * work on a set of files with more than one people (collaboration) * like the possibility to go back to earlier revisions (without manual hassle), or examine changes or make similar subtrees with some difference: called branches: same software/doc/whatever with small changes here and there (for whatever reason, eg. shipped to different customers, or deployed to different servers, etc... ) With the full power utilized, version tracking system can substitute * file-share (file-share is only better for static files like videos, CD-archives, etc...). For changing, evolving content version tracking system makes your life much better and your work cleaner ** with some rules and helper scripts, version tracking system can be suitable for project-tracking/overview/management. While powerful tools (like ofbiz.org) are often better for complex scenarios, version tracking tools are million times better than simple file-shares (often used) in any case when files evolve * wiki More about this in [Meta Wiki] |
| Note that the most current version (called the CVS head) is not for driving unless you know what you are doing. We use the released version from GenBoard/UnderDevelopment/FirmwareChanges so only get the CVS version if you want to test it on table. |
|
Avoid commiting files after moving between broken and proper systems. Win32 broken line endings might sneak into the CVS. It is not impossible to do right, but the easiest way is to checkout a different working directory instead of binary copying the files. |
| The last 3 steps are somewhat different for ssh, very easy to find out. |
| The last 3 steps are somewhat different for ssh, very easy to find out. |
| What is the best way to make bin/binary.pl from HEAD show up in the STABLE1_0 branch ? Do I have to cvs add bin/binary.pl and commit to the -r STABLE1_0 directory, or a better way is recommended so they are stored on server more efficiently ? |
| * [Meta Wiki] for more info on version tracking systems and advanced methods for collaboration/organizing information |