Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334771 - Determining virtual change sets for CVS
Summary: Determining virtual change sets for CVS
Status: CLOSED MOVED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-19 07:02 EST by Kilian Matt CLA
Modified: 2011-01-20 15:55 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kilian Matt CLA 2011-01-19 07:02:50 EST 
CVS does not support changesets, and one changeset per file commit is not feasible. A better approach would be to create a virtual change set, which groups file commits, based on date, author and commit message for example.
Comment 1 Kilian Matt CLA 2011-01-19 07:03:04 EST 
Alvaro, would that work for you?
Comment 2 Steffen Pingel CLA 2011-01-19 22:25:44 EST 
This would be a valuable addition. As discussed previously using an incremental approach that parses the cvs (r)log to discover change sets should be feasible for CVS.

In addition an extensible API should be provided to allow extensions such as task repository connectors that store change set information to provide these.
Comment 3 Alvaro Sanchez-Leon CLA 2011-01-20 10:29:22 EST 
Determining virtual changesets is needed and could be provided in multiple ways e.g. looking at the log as suggested below by Steffen, but also a wizard to help the user narrow down the list..  The resulting virtual changeset can then be stored by an application and address individual Diffs to the Versions API as needed.
Comment 4 Kilian Matt CLA 2011-01-20 11:29:55 EST 
Steffen: Are you thinking of that task-changeset mapping, which would be available for all different SCMs  - or do you mean that the task repository connector could influence just the grouping of check-ins to changeset for CVS or similiar systems? 

Alvaro: In order to avoid to mix some different concerns, this bug is just meant to provide some sort of change sets for CVS, which does not have change sets. 
Could you go ahead and file a bug for that wizard and user selection things you mentioned yesterday?
Comment 5 Steffen Pingel CLA 2011-01-20 15:55:52 EST 
(In reply to comment #4)
> Steffen: Are you thinking of that task-changeset mapping, which would be
> available for all different SCMs  - or do you mean that the task repository
> connector could influence just the grouping of check-ins to changeset for CVS or
> similiar systems?

Yes, I was more thinking of providing a task to change set mapping but I now realize that that's a separate enhancement and out of scope of this bug and we already have a bug for that: bug 197924: [team] provide a way to get from a task to a list of modified resources and CVS history entries .
Comment 6 Eclipse Webmaster CLA 2022-11-15 11:45:08 EST 
Mylyn has been restructured, and our issue tracking has moved to GitHub [1].

We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub.

[1] https://github.com/orgs/eclipse-mylyn