From: Junio C Hamano <junkio@cox.net>
To: Marco Costalba <mcostalba@yahoo.it>
Cc: Linus Torvalds <torvalds@osdl.org>,
Catalin Marinas <catalin.marinas@gmail.com>,
Petr Baudis <pasky@suse.cz>,
git@vger.kernel.org
Subject: Re: [RFC] extending git-ls-files --exclude.
Date: Mon, 25 Jul 2005 15:06:18 -0700 [thread overview]
Message-ID: <7vll3uh76t.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20050725213456.23910.qmail@web26310.mail.ukl.yahoo.com
Marco Costalba <mcostalba@yahoo.it> writes:
> This cumulative effect brakes local scoping of .gitignore files in
> corresponding subdirectory.
>
> As example in a directory A we can have a .gitignore file with
>
> !foo.html
> *.html
>
> because we want to special case 'that' foo.html in 'that'
> directory.
I guess that !foo.html I wrote was a bad example of special case
not being specific enough. Saying "!/foo.html" should work
[*1*], so I think "cumulative effect _breaks_" is a bit too strong
a word.
Having said that,...
> This can be powerful and flexible but also prone to errors.
While I also suspect it _might_ be prone to user errors, at
least to some classes of users, Catalin (and Peter as well I
suspect, although I may be mistaken by what he originally meant
by "cumulative") seems to think it is OK. As a developer of
another Porcelain (qgit), your input is as valuable as others,
so...
BTW, I am CC'ing git list because I saw you forwarded your
entire message to the list as a quoted message form. Please do
not do that. I cannot distinguish a message like that with a
message with nothing but quote and no original contents, which I
normally discard without even reading.
[Footnote]
*1* I just tried, and it seems to work.
$ rm -f .gitignore ppc/.gitignore
$ (echo '!/foo.bar'; echo '*.bar') >.gitignore
$ for i in foo.bar baz.bar; do date >$i; date >ppc/$i; done
$ git-ls-files --others --exclude-per-directory=.gitignore | grep '\.bar'
foo.bar
$ rm -f .gitignore ppc/.gitignore
next parent reply other threads:[~2005-07-25 22:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050725213456.23910.qmail@web26310.mail.ukl.yahoo.com>
2005-07-25 22:06 ` Junio C Hamano [this message]
2005-07-25 6:41 [RFC] extending git-ls-files --exclude Marco Costalba
2005-07-25 7:32 ` Junio C Hamano
2005-07-25 19:56 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2005-07-21 20:23 [PATCH 1/1] Tell vim the textwidth is 75 Bryan larsen
2005-07-22 2:50 ` Junio C Hamano
2005-07-22 10:37 ` Catalin Marinas
2005-07-22 19:24 ` Sam Ravnborg
2005-07-22 20:39 ` Junio C Hamano
2005-07-22 20:59 ` Petr Baudis
2005-07-24 22:49 ` [RFC] extending git-ls-files --exclude Junio C Hamano
2005-07-25 9:19 ` Catalin Marinas
2005-07-25 19:58 ` Junio C Hamano
2005-07-25 20:09 ` Linus Torvalds
2005-07-25 20:27 ` Junio C Hamano
2005-07-25 20:51 ` Catalin Marinas
2005-07-28 15:57 ` Petr Baudis
2005-07-25 20:59 ` Catalin Marinas
2005-07-28 15:52 ` Petr Baudis
2005-07-28 16:04 ` A Large Angry SCM
2005-07-28 19:25 ` Matthias Urlichs
2005-07-29 7:21 ` Petr Baudis
2005-07-29 7:37 ` Matthias Urlichs
2005-07-29 13:49 ` A Large Angry SCM
2005-07-29 5:04 ` Junio C Hamano
2005-07-29 7:36 ` Petr Baudis
2005-07-29 8:24 ` Junio C Hamano
2005-07-29 8:41 ` Petr Baudis
2005-08-01 16:14 ` Wayne Scott
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=7vll3uh76t.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=mcostalba@yahoo.it \
--cc=pasky@suse.cz \
--cc=torvalds@osdl.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).