All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wink Saville <wink@saville.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Using git with Eclipse
Date: Mon, 10 Dec 2007 21:55:41 -0800	[thread overview]
Message-ID: <475E265D.5090106@saville.com> (raw)
In-Reply-To: <20071211024442.GJ14735@spearce.org>

Shawn O. Pearce wrote:
> Wink Saville <wink@saville.com> wrote:
>   
>> I'm trying to use git on an Eclipse workspace and the .metadata 
>> directory is chock full of files and was wondering what, if anything, 
>> should be ignored. At the moment .history looks like a candidate for 
>> ignoring there are probably others.
>>     
>
> Ignore all of .metadata; its Eclipse private state that you don't
> want to version.  I'd add it to .git/info/exclude so its ignored only
> in the repository that is using Eclipse, rather than in .gitignore
> (which is published).
>
>   
Shawn,

I added .metadata to exclude then used git rm to remove
.metadata from the repository. I then cloned that
repository to see how Eclipse would work. (As part of  my
workflow I use git as a backup so I wanted to see what would
happen when I "restored".)

As I'm sure you know with the metadata gone my existing projects
in the Ui were gone and they have to be recreated as well as
some Eclipse and plugin specific configuration.
I understand you and others are working on an Eclipse plugin
for git, will it also ignore . metadata?

Do you need any testing done or is it too early? I'd be glad to
test if you feel its solid enough that I won't lose data or if it
uses a separate different repo then I could use both.

Regards,

Wink Saville

  reply	other threads:[~2007-12-11  5:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 22:42 Using git with Eclipse Wink Saville
2007-12-11  2:44 ` Shawn O. Pearce
2007-12-11  5:55   ` Wink Saville [this message]
2007-12-11 15:14     ` Jing Xue
2007-12-12  0:29     ` Robin Rosenberg
2007-12-12  6:07       ` Wink Saville
2007-12-13 21:23         ` Robin Rosenberg
2007-12-13 22:41           ` Wink Saville

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=475E265D.5090106@saville.com \
    --to=wink@saville.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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.