git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yakov Lerner" <iler.ml@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: multiple .gitignore-s
Date: Mon, 23 Apr 2007 13:51:48 +0300	[thread overview]
Message-ID: <f36b08ee0704230351l19eae2dbl3e1ce7287658be06@mail.gmail.com> (raw)
In-Reply-To: <7vwt04krp8.fsf@assigned-by-dhcp.cox.net>

On 4/23/07, Junio C Hamano <junkio@cox.net> wrote:
> "Yakov Lerner" <iler.ml@gmail.com> writes:
>
> > If repo has toplevel .gitignore, and subdir A/B
> > has also .gitignore, then how these two .gitignore-s
> > interact to affect A/B ? Are they shadowed, or accumulated ?
>
> Study "Exclude Patterns" section of git-ls-files documentation,
> perhaps?

Thanks
Yakov

      reply	other threads:[~2007-04-23 10:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-22 21:36 multiple .gitignore-s Yakov Lerner
2007-04-22 21:46 ` Junio C Hamano
2007-04-23 10:51   ` Yakov Lerner [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

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

  git send-email \
    --in-reply-to=f36b08ee0704230351l19eae2dbl3e1ce7287658be06@mail.gmail.com \
    --to=iler.ml@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).