git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Mark Wartman <markwartman1@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to Not Track .metadata
Date: Thu, 14 May 2020 00:51:14 +0000	[thread overview]
Message-ID: <20200514005114.GH6605@camp.crustytoothpaste.net> (raw)
In-Reply-To: <DD111BBE-F04A-4E44-99FE-5672FF2934B5@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]

On 2020-05-13 at 23:51:44, Mark Wartman wrote:
> Hello,
> 
> In a sentence, I cannot get Git to not track a .metadata file.  How would I correct this?
> 
> Please see .txt files as the mail system would not allow me to mail it.
> 
> I can say that I did try running: git clean -n
> I realize that the -n is for a dry run but it did not return anything anyway.
> 
> I am using:
> git version 2.10.1 (Apple Git-78)
> OS X El Capitan version 10.11.6
> 
> 
> Thanks,
> 
> Mark Wartman
> 

> 
> 
> I have cloned a repository that a particular .metadata file was pushed too.  This .metadata file seems to be causing me many git conflicts and other issues with Eclipse.
> 
> So lets say I had a folder named rev.  I navigated into the folder rev which there was nothing in there to start with.  I ran the command:
> git clone https://github.com/BenArayathel/0427Java.git
> 
> So now 0427Java lives inside of rev
> 
> Then inside of 0427Java there is folder called usf-batch-workspace
> 
> Inside of usf-batch-workspace are java projects that I and my fellow batch-mates work on.  I have a .gitignore in all three of:
> java-project, usr-batch-workspace, and 0427Java and all three .gitignore???s are the same.

I believe your problem is that the .metadata directory is already
tracked.  A .gitignore file has no effect on files that are already
tracked.

If you want to have those files ignored, then you need to remove them
first, by running "git rm -r --cached usf-batch-workspace/.metadata" if
you want to keep the files locally and without the "--cached" if you
want to remove them from the working tree as well.

Note that the files will be removed from others' systems when they pull
that change into their branches, which is by design.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      reply	other threads:[~2020-05-14  0:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 23:51 How to Not Track .metadata Mark Wartman
2020-05-14  0:51 ` brian m. carlson [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200514005114.GH6605@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=markwartman1@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).