Community
Participate
Working Groups
Build Identifier: M20090211-1700 Modern day revision control tools will commit a set of files as a single work unit easily allowing anyone to find all modified files for that specific commit at a later time (as a 'change set'). CVS lacks this functionality (although this information may be obtained by alternate queries)! For this exact reason most companies that still use CVS have a corporate policy which require that a list of modified files (change set) be included in the commit comment. As useful as it may be, this is painfully annoying and laborious. Which is why so many developers omit this information and breach directives. It is especially frustrating to know that CVS actually knows the file set being committed as it displays it in several views in the 'Change' panel bellow the comment. It would be a HUGE benefit if we could automatically include this list of files within the comment. This could be achieved in one of several ways... 1. Using the 'Comment Template', a script variable could be reserved for this purpose such that the variable is replaced with the listing of files. An few examples of such variable could be $FILES or $CHANGE_SET or anything as such. 2. A check-box could be provided bellow the comment text area whereby when it is checked, the file list is automatically appended to the end of the comment. 3. A 'Copy' and/or 'Paste' button is placed next to the series of buttons already found to the right of the 'Changes' panel. By pressing the 'Copy' button, the list of files is copied to the clip board. And by pressing the 'Paste' button, the list of files is inserted at the cursor location of the comment. As an added 'nice to have', if we could also choose the formatting of the file list (Flat or Compressed Folder), that would be even better. Reproducible: Always Steps to Reproduce: n/a
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant please remove the stalebug whiteboard tag.
