| Summary: | Search on comment field | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Andrew Irvine <airvine> |
| Component: | Team | Assignee: | Platform-VCM-Inbox <platform-vcm-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | knut_radloff |
| Version: | 2.1 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Andrew Irvine
Cool idea. It would be slow, but faster than checking by hand. A second approach that would be faster for searches, but more overhead for storage would be to create the concept of an update. An update simply groups all files associated with the action. So if I changed five files for one PR the update would store these file file names somewhere. Other usefull information would be the date, the branch and the comment. For example: airvine.1 20021126 R2.1 [comment] file1.version file2.version file3.version Currently if I look at the Resource History one of the fields I am presented is the author. That field could be changed to be the 'update'; rather than seeing airvine, I would see airvine.[number]. Thus if I am interested in airvine.26 I simply view that file and get all the information associated with it. This information could be stored at the time of commit, behind the scenes so there is no extra overhead for the user. *** Bug 60501 has been marked as a duplicate of this bug. *** The sync view now supports change sets. If this is not adequate for your needs, please reopen. |