git has replaced cvs as the version control system for drupal. -
There is a number of articles on to how handle git
but they don't really address the needs of site maintainers.
I am aware that this is a developers' group but since I found no better place to turn to...
... let me git it a try, anyway.
I have found no article specifically dealing with the needs of drupal admins
when having to MOVE FROM CVS TO GIT ON PRODUCTIVE SITES.
Let me ask a couple of questions as a site admin on Linux systems
on what to do in order to successfully move to git.
--> Actually I am going to tell you how I used to do things via cvs
hoping to get hands-on tips on how to do them via git.
1.0 Install specific module version via cvs [e.g. "captcha"]
I used to:
cd /var/www/drupal/sites/all/modules
sudo cvs -z6 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal-contribcheckout -r DRUPAL-6--1-8-BETA4 -d captcha contributions/modules/captcha
1.1 Install specific module version via git
--> ???
2.0 Display available module updates in drupal
I used to:
do this via cvs_deploy
I understand that "cvs_deploy" is now replaced by "git_deploy"
which still comes in a development version and has very low usage statistics (81).
--> is it reliable enough to run on productive sites??
2.1 Update modules to specific module version via cvs [e.g. "captcha"]
cd /var/www/drupal/sites/all/modules/captcha
cvs update -r DRUPAL-6--2-0-BETA4 -dP
2.1.1 updating modules to specific module version via git
--> ???
3.0 update drupal to a specific version via cvs [e.g. "DRUPAL-6-20"]
sudo su
cd
--> I used to run a mini-script which looks like:
cd /var/www/drupal; cvs -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal update -r DRUPAL-6-20 -dP
3.1 updating drupal to a specific version via git
--> ???
Many thanks for helping me out on this!
charles