Community
Participate
Working Groups
When I went to synchronize my workspace, I hit some issues with the view being overloaded with files that should be in .gitignore...
Created attachment 176428 [details] Synchronizing HEAD vs. 0.8.4
This change should fix this issue: http://egit.eclipse.org/r/1297
Fixed with 057173ac27c0724152f91869133dfa163d07fc6a.
I do still see resources which are listed in .gitignore. 057173ac27c0724152f91869133dfa163d07fc6a does only exclude resources via Team.isIgnoredHint which has no clue about .gitignore. You have to use a WorkingTreeIterator which has a method isEntryIgnored().
That's correct, only derived resources are accounted for atm.
(In reply to comment #4) > You have to use a WorkingTreeIterator which has a method isEntryIgnored(). I'll try to use NotIgnoredFilter on TreeWalk instead of WorkingTreeIterator.
Change set: http://egit.eclipse.org/r/1305
Fixed with d97e8442fb3d5981d5f279e4a13af9a1fdcb5ae6.
I'm seeing this issue happen on a git-svn clone of Jetty 7 repository (svn+ssh://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty) created using git 1.7.1 on Ubuntu 10.10 with --stdlayout setting. I'm using EGit 0.11.3, and trying to synchronize working copy with a local branch.
(In reply to comment #9) > I'm seeing this issue happen on a git-svn clone of Jetty 7 repository > (svn+ssh://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty) created using > git 1.7.1 on Ubuntu 10.10 with --stdlayout setting. > > I'm using EGit 0.11.3, and trying to synchronize working copy with a local > branch. Thanks for reporting this Michael. I've already push change: http://egit.eclipse.org/r/#change,2696 that should fix this issue. This change also contains unit test that should prevent from regressions in feature.
I see this too. Ubuntu 10.04, Git 1.7.3, EGit: 1.0.0.201106090707-r Eclipse Indigo: Build id: 20110615-0604
[Batch change] Remove passed Target Milestones If anyone on CC list is going to fix/implement this, feel free to assign a new, post-1.3/2.0, target milestone.
I think this has been fixed some time ago.
*** Bug 330019 has been marked as a duplicate of this bug. ***