From: Shawn Pearce <spearce@spearce.org>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: git@vger.kernel.org
Subject: Re: Can the git exclude files mask out whole directories?
Date: Mon, 18 Sep 2006 14:32:20 -0400 [thread overview]
Message-ID: <20060918183220.GA31371@spearce.org> (raw)
In-Reply-To: <1158604087.28026.160.camel@okra.transitives.com>
Alex Bennee <kernel-hacker@bennee.com> wrote:
> I may be being a bit dim but according to the man page I should be able
> to specify paths with /'s in them. I want to exclude all CVS directories
> so I can commit stuff. I have tried:
>
> #
> # Ignore CVS files
> #
> */CVS/*
Just use CVS in your info/exclude file:
#
# Ignore CVS files
#
CVS
> to my exclude file but that seems suboptimal. Besides I'll also want to
> be ignoring whole build directories later. Have I subtly misunderstood
> the man page?
I ignore my build directories all the time by just putting their
names in .gitignore, with no trailing /.
--
Shawn.
prev parent reply other threads:[~2006-09-18 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 18:28 Can the git exclude files mask out whole directories? Alex Bennee
2006-09-18 18:32 ` Shawn Pearce [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=20060918183220.GA31371@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=kernel-hacker@bennee.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.
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).