"Live" Changelogging for CVS

 

My problem is that I often forgot what I have changed in my software when I do a cvs-check in. So I have to lookup my code for changes. If this could be automated, it would be great.

So can anyone tell me if there is a tool or something which can lookup my code (I'm using C#) for specific comments, that I add if I change something and write these comments to a file, so I can use it for cvs checkin?

An example: 

//BUGFIX: This Program part was changed
//IMPROVED: This is a new Function
...ProgramCode...

The program should read my source files and recognize the comments with BUGFIX and IMPROVED . These comments should be written to a file. After they a written the lines with BUGFIX and IMPROVED should be removed from my sources. It should be possible to declare new tags.

I would be happy if somebody can give me an advice.

Another answer, concerning the alternative method of writing the log-file yourself.

A simple VBScript could do that job of appending (see vbs-script-to-append-to-a-specified-text-file). Display an InputBox, enter the text and let the script append it to a predefined file.

I think the way I would do it is the following

  • Install Launchy
  • Place a txt-File in a directory used by Launchy

    • Whenever you changed something, open the textfile using Launchy, append your changes, save and close the file again.

    You can do all this with the keyboard, it's just some extra keystrokes (open Launchy and type the first few letters of your txt-File's name) and once you are done you're back to your IDE.

    I don't know how to do what you want, but here's how I work with CVS to avoid this problem in first place :)

    Only work on one feature/bugfix a time, and commit it after you're done.

    Instead of adding a BUGFIX-tag into your sourcecode, commit the changed files immediately after you fixed the bug (and tested your fix). This is the moment when you know exactly what you did, and why and how you did it.
    This leaves you with a clean sandbox, so you don't have to bother about changed files when adding the next feature/fixing the next bug.

    When working on features taking days or weeks, make sure to commit your progress, even if the feature is not complete yet (do not break the build though, when others rely on it).

    And if you develop a new feature that you can not commit yet and you have to do an urgent bugfix, commit that in a different sandbox and use CVS update on your working copy to merge the bugfix when necessary.

    链接地址: http://www.djcxy.com/p/64840.html

    上一篇: 配置代码协作者根据所有权分配审阅者

    下一篇: CVS的“Live”更改日志记录