Commit across multiple directories causes this behavior

[Mala T]

Hi

I have a script that generates a task number for each commit and adds it to the log message. This is for release and deployment purposes.
I see the following behavior: When someone commits files in multiple directories with the same commit command, then it is generating one task number for each directory.
For example,
I see the following.
---------------------------------------------------------------------
Added files:
 Util/tistools/com/sbc/tis/tools: Tag: Br_04-16-2004_CRMR2A_Dev
                                  TisDef.java
                                  ChangePasswordHelper.java
                                  Logger.java
                                  ValidatePasswordEJBHelper.java 
                                 

Log message:
 Task44: TAR#xxxx WR#4146a
 Task44: initial import of tis Util/tistools.  Build this project as tistools.jar
 Task44:

Added files:
 Util/tistools/com/sbc/tis/logging: Tag: Br_04-16-2004_CRMR2A_Dev
                                    Timecalc2.java Log.java
                                    Formatter.java Logger.java
                                    FileMonitor.java.bak 
                                   

Log message:
 Task45: Task44: TAR#xxxx WR#4146a
 Task45: Task44: initial import of tis Util/tistools.  Build this project as tistools.jar
 Task45: Task44:

--------------------------------------------------------------------
CVS is treating each directory as a separate commit, it seems. For the same log message, it is adding multiple task numbers.Is there anyway I can modify this behavior? i.e get cvs to treat one commit, even if spanning multiple directories as just one commit command? I also see that when users check in thro' an IDE like eclipse, it adds the task number to each line of the log message. Is there anyway to prevent this?

I would appreciate any responses.
Thanks,
Mala

---

Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢