git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aleksey Komarov <leeeeha@gmail.com>
To: git@vger.kernel.org
Subject: submodule: allow submodule directory in gitignore
Date: Mon, 12 Oct 2015 13:30:10 +0700	[thread overview]
Message-ID: <561B5372.7040508@gmail.com> (raw)

Hi all!

I'm sorry if the letter came twice. I have troubles with my post client.

I want to organize my repository so its submodules would be located at the root
of repository. I'm trying to create .gitignore to ignore all files and don't
ignore directories at the same time:

$ cat .gitignore
*
!*/

Now, I'm trying to add a submodule to my repository, but fail to understand why
my .gitignore prevents it from being added. I use the following command to check
if my submodule will be ignored or not:

$ git add --dry-run --ignore-missing c/

I have noticed that result of this check is different when directory c/ already
exists and when it still doesn't by the time of the check.
The described behavior is illustrated by the following example:

$ mkdir git_test
$ cd git_test
$ git init
Initialized empty Git repository in D:/temp/git_test/.git/
$ echo \* >> .gitignore
$ echo \!\*\/ >> .gitignore
$ git add --dry-run --ignore-missing c/
The following paths are ignored by one of your .gitignore files:
c/
Use -f if you really want to add them.
$ mkdir c
$ git add --dry-run --ignore-missing c/
$

Is this behavior expected? If yes, where can I read about it? Which part of the
Git documentation should I consult?
How should I correct my .gitignore to pass this check in both cases, when
directory c/ exists and when it doesn't?

             reply	other threads:[~2015-10-12  6:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12  6:30 Aleksey Komarov [this message]
2015-10-16  9:33 ` submodule: allow submodule directory in gitignore Aleksey Komarov
2015-10-17 12:46 ` Jiang Xin
2015-10-19  2:24   ` Aleksey Komarov

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=561B5372.7040508@gmail.com \
    --to=leeeeha@gmail.com \
    --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).