Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351248 - Patch format file comparison
Summary: Patch format file comparison
Status: CLOSED DUPLICATE of bug 407950
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-05 18:30 EDT by Jacek Kolodziejczyk CLA
Modified: 2013-09-29 15:53 EDT (History)
4 users (show)

See Also:

Attachments
Example of the patch format displayed by Git Gui (96.22 KB, image/jpeg)
2011-07-06 04:04 EDT, Jacek Kolodziejczyk CLA 		no flags Details
View All 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 Jacek Kolodziejczyk CLA 2011-07-05 18:30:51 EDT 
Build Identifier:  I20110613-1736

Path format file comparison shows only changes with little context. It is the most communicative and ergonomic way to present file modifications. Can prevent scrolling large files to see a single line change, which is necessary with the present comparison view.

Reproducible: Always
Comment 1 Jacek Kolodziejczyk CLA 2011-07-06 04:04:12 EDT 
Created attachment 199167 [details]
Example of the patch format displayed by Git Gui
Comment 2 Matthias Sohn CLA 2011-08-10 08:21:44 EDT 
Did you try the diff pane in the history view [1] or the diff tab in the commit viewer [2] ?

[1] http://wiki.eclipse.org/EGit/User_Guide#View_Diff_for_a_Commit
[2] http://wiki.eclipse.org/EGit/User_Guide#Viewing_Commits
Comment 3 Jacek Kolodziejczyk CLA 2011-08-20 15:32:31 EDT 
I haven't try those. They look good, but can see the changes this way before I create the commit, during inspecting the staged modifications?
Comment 4 Robin Stocker CLA 2013-09-29 15:53:47 EDT 
This would be very useful. Let's track this in bug 407950, which has some more details on how to implement this.

*** This bug has been marked as a duplicate of bug 407950 ***