From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Stephen Bannasch <stephen.bannasch@deanbrook.org>,
"Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org, Scott Cytacki <scytacki@fastmail.fm>
Subject: Re: egit problem with sym linked eclipse project dirs
Date: Tue, 13 Jan 2009 22:37:11 +0100 [thread overview]
Message-ID: <200901132237.11946.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <p0624081cc5928e2885fd@[192.168.1.114]>
> To hack around Eclipse's problem with projects in nested directories
> I clone a repo and then create a new top-level dir that just has
> symbolic links to all the project directories.
>
> However when I Team/Share with git using egit the resources become
> untracked when displayed in Eclipse -- they still are tracked however
> when I check from the command line.
I've seen this too, but so far not got myself to actually fix it. I think it has do with
that we ask eclipse project for it's path end there we gets off track. Thanks
for providing a good example that help "someone" to fix it.
Could you add an issue at http://code.google.com/p/egit/issues/list and maybe
include a tar ball with a simple project displaying this behaviour? (with a note
that the symlinks makes this impossible to recreate on Windows).
-- robin
next prev parent reply other threads:[~2009-01-13 21:38 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 [this message]
2009-01-13 23:27 ` Stephen Bannasch
2009-01-23 1:56 ` Stephen Bannasch
2009-01-23 21:33 ` Robin Rosenberg
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=200901132237.11946.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=scytacki@fastmail.fm \
--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.