From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Stephen Bannasch <stephen.bannasch@deanbrook.org>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: egit problem with sym linked eclipse project dirs
Date: Fri, 23 Jan 2009 22:33:59 +0100 [thread overview]
Message-ID: <200901232233.59232.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <p06240812c59ed365d694@[192.168.1.106]>
fredag 23 januari 2009 02:56:16 skrev Stephen Bannasch:
> At 6:27 PM -0500 1/13/09, Stephen Bannasch wrote:
...
> >Done: http://code.google.com/p/egit/issues/detail?id=52
> >
> >Fxing this will make using Eclipse and Git together SO much nicer!
>
> Robin and Shawn,
>
> Can you suggest where in the egit code I should look to see if I can fix this?
There may be more than one place.
Take a look at GitResourceDecorator.
We map from resources using code like this:
RepositoryMapping.getMapping(rsrc) // <-- prime suspect
Repository.getRepoRelativePath(rsrc)
Repository.getWorkDir
Repository.isResourceChanged
I'm not entirely sure this is the correct way, but it probably has no
bearing on your problem.
GitResourceDecorator decorator = getActiveDecorator();
It would be nice with a unit test for this. (Not necessarily the decorator,
but the methods used for it).
-- robin
next prev parent reply other threads:[~2009-01-23 21:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 20:00 egit problem with sym linked eclipse project dirs Stephen Bannasch
2009-01-13 21:37 ` Robin Rosenberg
2009-01-13 23:27 ` Stephen Bannasch
2009-01-23 1:56 ` Stephen Bannasch
2009-01-23 21:33 ` Robin Rosenberg [this message]
2009-03-11 22:17 ` [EGIT RFC PATCH(was Re: egit problem with sym linked eclipse project dirs)] Add some support for symlinked projects Robin Rosenberg
2009-03-12 2:57 ` Stephen Bannasch
2009-03-12 6:56 ` Robin Rosenberg
2009-03-18 16:02 ` Stephen Bannasch
2009-03-18 21:09 ` Robin Rosenberg
2009-03-18 21:10 ` Robin Rosenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200901232233.59232.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=stephen.bannasch@deanbrook.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.