All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: Chris Packham <judge.packham@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	jgit-dev@eclipse.org, egit-dev@eclipse.org
Subject: Re: Egit/Jgit support for relocated .git directories
Date: Sat, 07 Jul 2012 12:18:12 +0200	[thread overview]
Message-ID: <4FF80CE4.60303@dewire.com> (raw)
In-Reply-To: <4FE97057.3040609@gmail.com>

Chris Packham skrev 2012-06-26 10.18:
> Hi,
>
> This is a bit of a secondhand bug report/query so sorry if the details
> are a bit sketchy.
>
> Since git 1.7.8:
>
> ``When populating a new submodule directory with "git submodule init",
> the $GIT_DIR metainformation directory for submodules is created inside
> $GIT_DIR/modules/<name>/ directory of the superproject and referenced
> via the gitfile mechanism. This is to make it possible to switch
> between commits in the superproject that has and does not have the
> submodule in the tree without re-cloning.''
>
> I've had several colleagues at work tell me that with the relocated
> $GIT_DIR the Egit integration with eclipse doesn't work. I can't really
> qualify "doesn't work" but from what I've been told importing the
> project works but blaming/annotating doesn't.
>
> I believe the gitfile mechanism isn't new but it possibly hasn't been
> used by many Egit/Jgit users. Can anyone confirm if it is supported by
> Egit/Jgit (and I'm barking up the wrong tree).

It is supported. There is however a commit as late as in May that relates
to gitfile, so you may need 2.0.

-- robin

      parent reply	other threads:[~2012-07-07 10:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26  8:18 Egit/Jgit support for relocated .git directories Chris Packham
2012-06-26 15:40 ` Shawn Pearce
2012-06-28  8:16   ` Chris Packham
2012-07-07 10:18 ` Robin Rosenberg [this message]

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=4FF80CE4.60303@dewire.com \
    --to=robin.rosenberg@dewire.com \
    --cc=egit-dev@eclipse.org \
    --cc=git@vger.kernel.org \
    --cc=jgit-dev@eclipse.org \
    --cc=judge.packham@gmail.com \
    /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.