All of lore.kernel.org
 help / color / mirror / Atom feed
From: "3Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: git@vger.kernel.org
Subject: Re: Q: Ignore ./foo, but not script/foo
Date: Thu, 19 Jul 2018 10:01:46 +0200	[thread overview]
Message-ID: <8736wfd579.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <5B503FF0020000A10002C6B5@gwsmtp1.uni-regensburg.de>


On Thu, Jul 19 2018, Ulrich Windl wrote:

> Hi!
>
> I have a (simple) question I could not answer elegantly from the gitignore(5) manual page:
>
> A project produces a "foo" binary in the root directory that I want to ignore (So I put "foo" into .gitignore)
> Unfortunately I found out taht I cannot have a "script/foo" added while "foo" is in .gitignore.
> So I changed "foo" to "./foo" in .gitignore. I can could add "script/foo", but now "foo" is not ignored any more!
>
> Is there as solution other than:?
> --
> foo
> !script/foo
> !bla/foo
> #etc.

The solution is to just do:

    echo /foo >.gitignore

Then it'll ignore the top-level /foo, but nothing else. How did you come
up with this "./" syntax? It's not understood by gitignore. From
gitignore(5):

   A leading slash matches the beginning of the pathname. For example,
   "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c".

  reply	other threads:[~2018-07-19  8:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19  7:38 Q: Ignore ./foo, but not script/foo Ulrich Windl
2018-07-19  8:01 ` 3Ævar Arnfjörð Bjarmason [this message]
2018-07-19  9:06   ` Timothy Rice
2018-07-19  9:22     ` Konstantin Khomoutov
2018-07-19  9:30     ` Ævar Arnfjörð Bjarmason
     [not found] ` <CA+xP2SZJ0VN0Y7SChAx1a8joVMKMU2R9d0je801i=9SuLicF3w@mail.gmail.com>
2018-07-19 11:00   ` Antw: " Ulrich Windl

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=8736wfd579.fsf@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=Ulrich.Windl@rz.uni-regensburg.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 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.