Bugzilla – Full Text Bug Listing
| Summary: | [Commands] CVS Module Folder display doesn't handle comments in 'module' | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | neil_buesing |
| Component: | CVS | Assignee: | platform-cvs-inbox <platform-cvs-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | Keywords: | helpwanted |
| Version: | 2.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
Looks like another undocumented CVS "feature". The CVS spec does not mention anything about comments at the end of module definition lines. Furthermore, the fact that the server provides them when executing a "cvs checout -c" is, IMHO, a server bug (i.e. lines that start with # are not provided so it makes since that other comments shouldn't be either). Should be easy to fix though. Post 3.0 There is currently no plan to address this item. As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |
If you have a following entry (with a trailing comment) in CVSROOT/modules like this project project #ProjectOwner A, BackupOwner B You will get the following result in the 'CVS Repositories View' -project # 0 # A, # B # BackupOwner # ProjectOwner Modules w/out the comments will behave correctly (and you can inspect the contents of the module) as it appears in the cvs folder (as referenced by the project).