Bug 408977 - Pull operation should only refresh changed resources
Summary: Pull operation should only refresh changed resources
Status: NEW
Alias: None
Product: EGit
Classification: Technology
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-24 08:58 EDT by Robert Munteanu CLA
Modified: 2013-06-03 15:32 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 Robert Munteanu CLA 2013-05-24 08:58:39 EDT 
I see that everytime I perform a pull a full reindex of the repository is performed. This is terribly inefficient with large repositories like mine and leads to a sluggish Eclipse for a  minute or two. I have pull set up to rebase automatically, if that makes a difference.

I think that the pull operation should use the information on what has changed and only refresh the changed resources.

Running Eclipse EGit 3.0.0.201305080800-m7 on Eclipse Kepler, Linux x86_64.
Comment 1 Robin Rosenberg CLA 2013-06-03 15:32:35 EDT 
Rebase or not is not relevant. It's laziness on our side. All modifying commands in JGit needs to export information out what files and directories have changed. It is not just pull.