PUBLIC MARKS with tags cvs & dev

Git User's Manual

Most software version control systems provide mechanisms for branching into multiple lines of development and merging source code from one development line into another. However, the techniques, policies and guidelines for using these mechanisms are often misapplied or not fully understood. This is unfortunate, since the use or misuse of branching and merging can make or break a parallel software development project. Streamed Lines is a pattern language for organizing related lines of development into appropriately diverging and converging streams of source code changes.

cheat sheets (also known as reference cards) that you can print out and keep by your computer. There is a cheat sheet for just about anything and we aim to have the best coverage of cheat sheets available on the web.

cheat sheets (also known as reference cards) that you can print out and keep by your computer. There is a cheat sheet for just about anything and we aim to have the best coverage of cheat sheets available on the web.

Subversion, extension du célèbre outil de contrôle de version, apporte suffisamment d'innovations, tout en restant proche de son prédécesseur, pour justifier de sauter le pas. La transition pas à pas.

This page explains how I migrated the VideoLAN CVS repositories to Subversion while still allowing anonymous CVS access for users who did not want to move to Subversion. If you are a CVS user and have not yet fallen in love with Subversion, I suggest you have a look at this excellent project. In fact, I recommend to be familiar with Subversion before reading this document, because I may have missed important things.

As CVS is quite dated and Subversion (SVN) introduced some handy features (atomic transactions, Apache piggybacking, more convenient branching/tagging, tons of other improvements), we chose to go with SVN. The big question was: how to use it correctly?

As CVS is quite dated and Subversion (SVN) introduced some handy features (atomic transactions, Apache piggybacking, more convenient branching/tagging, tons of other improvements), we chose to go with SVN. The big question was: how to use it correctly?

Tutorial d'installation et d'utilisation d'un serveur CVS.

* Automatically generates a patch-set log from CVS check-in comments * User-defined color-coded database queries * Web-based administration of the CVSROOT/passwd file * Built-in repository browser * Built-in Wiki * Very simple setup - a self-contained executable runs as CGI, from inetd, or as a stand-alone web server * Minimal memory, disk and CPU requirements - works on old hardware * Access permissions configurable separately for each user * Allows for anonymous users * Uses a built-in SQL database engine (SQLite) - no external RDBMS required * Tested under Linux - works on other versions of Unix. Also works under Windows * Can be run from a chroot jail for added security. * GNU Public License

* Automatically generates a patch-set log from CVS check-in comments * User-defined color-coded database queries * Web-based administration of the CVSROOT/passwd file * Built-in repository browser * Built-in Wiki * Very simple setup - a self-contained executable runs as CGI, from inetd, or as a stand-alone web server * Minimal memory, disk and CPU requirements - works on old hardware * Access permissions configurable separately for each user * Allows for anonymous users * Uses a built-in SQL database engine (SQLite) - no external RDBMS required * Tested under Linux - works on other versions of Unix. Also works under Windows * Can be run from a chroot jail for added security. * GNU Public License