Thanks for the quick reply.

Usage: cvs commit [-Rlf] [-m msg | -F logfile] [-r rev] files...
    -R          Process directories recursively.
    -l          Local directory only (not recursive).
    -f          Force the file to be committed; disables recursion.
    -F logfile  Read the log message from file.
    -m msg      Log message.
    -r rev      Commit to this branch or trunk revision.

I think this is the right track, but the comment "disables recursion" raises
a question.  If I do:

cvs commit -R -f -m "production deployed on 19 Dec 2007" *

Will cvs add this message to all the files (use the -R recursion) or just
the files in this directory (ignores -R)?

Cheers
Eric






Rick Genter wrote:
> 
>> From: [EMAIL PROTECTED] 
>> [mailto:[EMAIL PROTECTED] 
>> On Behalf Of eric63
>> Sent: Wednesday, December 19, 2007 12:34 PM
>> To: [email protected]
>> Subject: add log message to an unaltered file
>> 
>> 
>> Good morning,
>> 
>>   Is it possible to add a log message to a group of files 
>> that have not been
>> modified?  For example, I can do 'commit -m "message" *' to a 
>> bunch of files
>> but only if they have already been edited.
>> 
>>   We use the tag to contain a version number and I would like 
>> to have to
>> overwrite or add to the tag information.   I'd like to create 
>> a message that
>> will appear in $Log$.
>> 
>> Thanks
>> Eric
> 
> commit -f will force a commit, even if there are no changes. You will
> end up with a new revision number for the file, and if you want your
> $Log$ to reflect the new comment, I think you'll have to do an update
> after the commit -f.
> --
> Rick Genter
> Principal Software Engineer
> Silverlink Communications
> [EMAIL PROTECTED]
> www.silverlink.com
>  
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/add-log-message-to-an-unaltered-file-tp14423428p14425046.html
Sent from the Gnu - Cvs - Info mailing list archive at Nabble.com.



Reply via email to