Bug 300214 - [Sync View][Apply Patch] 'Merge' and 'Mark as merged' individual hunks
Summary: [Sync View][Apply Patch] 'Merge' and 'Mark as merged' individual hunks
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact: Tomasz Zarna CLA
URL: http://wiki.eclipse.org/Apply_patch_i...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-20 11:43 EST by Tomasz Zarna CLA
Modified: 2019-09-06 15:35 EDT (History)
1 user (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 Tomasz Zarna CLA 2010-01-20 11:43:14 EST 
Once bug 236169 is fixed, we should consider adding an option to apply individual hunks displayed in the Sync View. Current implementation proposed in bug 298923 allows to apply changes for a single file, but does not let you apply single hunk.
Comment 1 Tomasz Zarna CLA 2010-03-01 11:30:42 EST 
Same story with Mark as Merged for individual hunks once bug 300237 got fixed.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:31:24 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.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:35:49 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.