K B wrote:
Is your question: How can I retag the module? i.e. How can I move the tag from an older version to a more current one?
Yes, that's what I want to do. I've made some revisions to the module, which Civicspace wanted made before they can include it in future CS releases. After I made the revisions, Neil Drumm asked me to "make sure you tag it [1] so I can check it off my list [2]": http://civicspacelabs.org/home/node/12095 I assume that by "make sure you tag it" he meant, "retag it," so that's what I've been trying to do. K B also wrote:
If so, then you need to delete the tag first then tag it.
cvs tag -d DRUPAL-4-5 file(s)
I tried doing this but got the following message: "cvs tag: Not removing branch tag `DRUPAL-4-5' from `/cvs/drupal-contrib/contributions/modules/interwiki/CREDITS.txt,v'."
Note that this has a side effect: people who downloaded and used the old module will say they have the 4.5.0 version of the module, and then people who will download the module tomorrow will say that they have the same version.
This can lead to support nightmares, since two different pieces of code are tagged the same.
However, this seems to be common practice in contrib. I have discussed this on the list in the past, and it was suggested that a date be included in the tar ball name, but no action was taken on that.
I can see your point. In my case, however, the interwiki module is still new and not widely disseminated, so I think retagging would do more good than harm. --Sheldon
On Apr 5, 2005, at 1:53 PM, Sheldon Rampton wrote:
Is your question: How can I retag the module? i.e. How can I move the tag from an older version to a more current one?
Yes, that's what I want to do. I've made some revisions to the module, which Civicspace wanted made before they can include it in future CS releases. After I made the revisions, Neil Drumm asked me to "make sure you tag it [1] so I can check it off my list [2]":
http://civicspacelabs.org/home/node/12095
I assume that by "make sure you tag it" he meant, "retag it," so that's what I've been trying to do.
Drupal Contrib Branches Made Simple: Maintain a checkout of each branch, separately. cvs -d:pserver:your_user_name@cvs.drupal.org:/cvs/drupal-contrib login cvs -d:pserver:your_user_name@cvs.drupal.org:/cvs/drupal-contrib checkout -r DRUPAL-4-5 contributions When you need to update the 4.5 version of the module, go to your 4.5 directory and update it. cvs update -dP Then make your changes and commit them. cvs commit Repeat this for each branch that needs updates. You only need to branch a module *once*, when it is first available for a particular Drupal release. -- Jonathan Chaffer Applications Developer, structure:interactive (616) 364-7423 http://www.structureinteractive.com/
Furthermore, when you want to add your module to a branch, copy the directory to your checkout of that branch and then do a CVS Add and CVS Commit.
Drupal Contrib Branches Made Simple:
Maintain a checkout of each branch, separately. cvs -d:pserver:your_user_name@cvs.drupal.org:/cvs/drupal-contrib login cvs -d:pserver:your_user_name@cvs.drupal.org:/cvs/drupal-contrib checkout -r DRUPAL-4-5 contributions
When you need to update the 4.5 version of the module, go to your 4.5 directory and update it. cvs update -dP
Then make your changes and commit them. cvs commit
Repeat this for each branch that needs updates.
You only need to branch a module *once*, when it is first available for a particular Drupal release.
participants (3)
-
Jonathan Chaffer -
Moshe Weitzman -
Sheldon Rampton