| commit | 91f0daac8a1eae6d2c8c300ed98827c70a980e0a | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 10 Aug 2008 06:40:36 +0000 (9 23:40 -0700) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 10 Aug 2008 06:44:48 +0000 (9 23:44 -0700) | ||
| tree | 50e3fff5f8ac0c3db8dd13b4fef5ee2891caee73 | treesnapshot (tar.gz zip) |
| parent | 4a230ea18a898edc36406b26fa442eaf343c3fa6 | commitdiff |
Fix RepositoryMapping.getRepoRelativePath to honor linked resources
If a project resource is linked to a repository working directory we
should be locating the path of the resource within the repository by
the path it appears in the filesystem, not the path it appears at in
the Eclipse project structure. By using the filesystem location we
can ensure the paths match what C Git would see when accessing the
same resource.
By making this change we can now safely remove the subset concept
from RepositoryMapping as it was a crude form of trying to come up
with the same result when projects appeared within a repository.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
If a project resource is linked to a repository working directory we
should be locating the path of the resource within the repository by
the path it appears in the filesystem, not the path it appears at in
the Eclipse project structure. By using the filesystem location we
can ensure the paths match what C Git would see when accessing the
same resource.
By making this change we can now safely remove the subset concept
from RepositoryMapping as it was a crude form of trying to come up
with the same result when projects appeared within a repository.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>