Bug 117298 - [Change Sets] Create change set on apply patch
Summary: [Change Sets] Create change set on apply patch
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-21 06:23 EST by Markus Keller CLA
Modified: 2019-09-06 16:10 EDT (History)
0 users

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 Markus Keller CLA 2005-11-21 06:23:56 EST 
I20051116-1332

Usually, when I apply a CVS patch in my workspace, I want to release it afterwards. It would be convenient if the files touched by the apply patch wizard were grouped in a change set, such that I don't have to hunt for them in the sync view when I already had other outgoing changes.
Comment 1 Michael Valenta CLA 2005-11-24 10:42:25 EST 
Apply patch is provided by Compare
Comment 2 Michael Valenta CLA 2006-07-11 12:33:53 EDT 
What you would need to do is create
Comment 3 Markus Keller CLA 2007-05-07 13:06:57 EDT 
> What you would need to do is create
Hmm, I don't think that create <whitespace> will do the job ;-)
Comment 4 Michael Valenta CLA 2007-05-07 13:44:29 EDT 
I think it is safe to say that you can ignore comment 2. Perhaps I was going to say that if you create a change set ahead of time and make it the default change set, then the patched files would automatically be placed in the change set. 

However, I agree that it would be nice to have the Apply Patch wizard create a change set automatically and populate it with the patched files. It's a bit complicated since CVS provides the change set support but Apply Patch is located in compare.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:10:26 EDT 
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.