git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kai Schlamp <schlamp@gmx.de>
To: git@vger.kernel.org
Subject: Re: Beginner problem with .gitignore
Date: Tue, 21 Apr 2009 11:57:30 +0200	[thread overview]
Message-ID: <49ED988A.6030504@gmx.de> (raw)
In-Reply-To: <49ED8914.9090808@drmicha.warpmail.net>

Michael, thanks for the help. Comments below.

> By "is ignored", do you mean that git status doesn't show it? 

Yes, that is what I meant.

> git status does not recurse into subdirectories by default unless there 
> is at least one tracked file inside.

Ok. I justed tested this a bit. Let's say I have the following directory 
structure: "/a_dir/b_dir/c_dir"

And have a .gitignore with:
/a_dir
!/a_dir/b_dir/c_dir/

Now i put a file "a_file" in "c_dir".
And add the a_file with "git add /a_dir/b_dir/c_dir/a_file". Yes, a_file 
is tracked now.

I would have expected (after your information above) that if I create 
another file "b_file" in "c_dir" and check "git status" that this file 
is on the untracked file list now.
But it doesn't show up.
And this makes it quite hard to exclude a whole folder, but only include 
one of it's subfolders. I use git gui for commits. And I like it that 
newly added files show up as untracked files.
But in this case those files in those subdiretories won't.

Best regards,
Kai

  reply	other threads:[~2009-04-21 10:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 17:57 Beginner problem with .gitignore Kai Schlamp
2009-04-21  8:51 ` Michael J Gruber
2009-04-21  9:57   ` Kai Schlamp [this message]
2009-04-21 11:43     ` Michael J Gruber
2009-04-21 12:26       ` Kai Schlamp

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=49ED988A.6030504@gmx.de \
    --to=schlamp@gmx.de \
    --cc=git@vger.kernel.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 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 NNTP newsgroup(s).