From: Junio C Hamano <junkio@cox.net>
To: Marco Costalba <mcostalba@yahoo.it>
Cc: git@vger.kernel.org
Subject: Re: [RFC] extending git-ls-files --exclude.
Date: Mon, 25 Jul 2005 00:32:41 -0700 [thread overview]
Message-ID: <7vek9ns5ly.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050725064140.95259.qmail@web26304.mail.ukl.yahoo.com> (Marco Costalba's message of "Sun, 24 Jul 2005 23:41:40 -0700 (PDT)")
Marco Costalba <mcostalba@yahoo.it> writes:
> Are really necessary to have both --exclude-from=<file> and
> --exclude-per-directory=<name> ?
>
> Peraphs, if the file name of excluded list is the same for each directory,
> e.g. .gitignore or something similar, instead of --exclude-per-directory
> we can use a concept of file validity 'scope' and just use --exclude-from=<file>.
> If entering in a directory <file> is found its contents are appended and
> removed when leaving directory. A bad analogy can be with the use of
> recursive Makefile.
Pasky wants to have one of the files in ~/.git-something if I
understand correctly. I did not want to remove --exclude-from
for that reason.
> If we use the 'scope' logic we can just prepend path when
> adding entries and serach with with FNM_PATHNAME flag.
And I wanted for people's script and existing ignore files to
continue to work.
> Same comment as above, if prepending path when adding per
> directory contents we can simplify to always use FNM_PATHNAME flag.
Yes, but that means you need to always prepend the current
directory being looked at to get the original behaviour. The
way it was originally done without FNM_PATHNAME was far easier
to read, at least for me.
next prev parent reply other threads:[~2005-07-25 7:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 6:41 [RFC] extending git-ls-files --exclude Marco Costalba
2005-07-25 7:32 ` Junio C Hamano [this message]
2005-07-25 19:56 ` Junio C Hamano
[not found] <20050725213456.23910.qmail@web26310.mail.ukl.yahoo.com>
2005-07-25 22:06 ` 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=7vek9ns5ly.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=mcostalba@yahoo.it \
/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).