Hi Philip Thanks a lot for your reply. This changeLog and RELEASE_NOTES idea sound good. So when you have to release a module you need to edit these files to reflect your projects capibiliteis etc. Am I right?
There's one more thing I wanted to ask. I can update my module or file to a tag or a date in YYYY-MM-DD format. But how can I update a file to a older revision which is not tagged.
For example. Today I make 3 commits for a file. and only the first and last are tagged so say the file has revisions 1.1 1.2 and 1.3 Now I can update to 1.1 and 1.3 since they are tagged. How do I update to 1.2 ? If I want to check out 1.2 or see what the file contained, how do I do that.
regards Abhijeet D Mhatre
Date: Tue, 23 Sep 2003 09:31:48 +0530 (IST) From: Philip S Tellis philip@ncst.ernet.in Subject: Re: [ILUG-BOM] Can you put a comment for a tag in CVS To: "GNU/Linux Users Group, Mumbai, India" linuxers@mm.ilug-bom.org.in Message-ID: Pine.LNX.4.44.0309230928240.17356-100000@bigears.ncst.ernet.in Content-Type: TEXT/PLAIN; charset=US-ASCII
On Mon, 22 Sep 2003, Abhijeet Mhatre wrote:
I can put a comment when I "commit" my files. I find this feature very useful. Is there any way I can put comment when I "tag" my module for
Not that I know of. This is so since comments are attached to file revisions. A tag does not change the revision of a file, it merely tags an existing revision.
Checking the man page shows that -m can only be used with add, commit and import.
What is generally done though, is to maintain a version ChangeLog and RELEASE_NOTES that get tagged when you tag a module. People can then just check these files for the given tag, but no, it won't show up in cvs log or cvsweb.
-- Disease can be cured; fate is incurable. -- Chinese proverb
-----BEGIN GEEK CODE BLOCK----- GCS/ED/MU/TW d- s+: a- C+++ UL+++ P++++ L+++>$ E--- W+++ N- o-- K- w--- PS+ PE Y+ PGP+ t* X- R* tv b+ DI+++ D+ G++ e+++>$ h* r y ------END GEEK CODE BLOCK------