# [PATCH] Document core.excludesfile for git-add 5 messages from 2007-05-17 to 2007-05-17. Participants: Michael Hendricks, Junio C Hamano, Petr Baudis, Johan Herland. Thread: https://gitlist.dev/t/8189 ## Michael Hendricks, 2007-05-17 05:08 Subject: [PATCH] Document core.excludesfile for git-add Message-ID: <1179378530822-git-send-email-michael@ndrix.org> URL: https://gitlist.dev/e/1179378530822-git-send-email-michael%40ndrix.org ``` During the discussion of core.excludesfile in the user-manual, I realized that the configuration wasn't mentioned in the man pages. Signed-off-by: Michael Hendricks --- Documentation/git-add.txt | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt index 27b9c0f..a0c9f68 100644 --- a/Documentation/git-add.txt +++ b/Documentation/git-add.txt @@ -69,6 +69,15 @@ OPTIONS for command-line options). +Configuration +------------- + +The optional configuration variable 'core.excludesfile' indicates a path to a +file containing patterns of file names to exclude from git-add, similar to +$GIT_DIR/info/exclude. Patterns in the exclude file are used in addition to +those in info/exclude. See link:repository-layout.html[repository layout]. + + EXAMPLES -------- git-add Documentation/\\*.txt:: -- 1.5.2.rc3.39.gaf9b-dirty ``` ## Junio C Hamano, 2007-05-17 05:31 Subject: Re: [PATCH] Document core.excludesfile for git-add Message-ID: <7vwsz89ftr.fsf@assigned-by-dhcp.cox.net> URL: https://gitlist.dev/e/7vwsz89ftr.fsf%40assigned-by-dhcp.cox.net In-Reply-To: <1179378530822-git-send-email-michael@ndrix.org> ``` Thanks, but wouldn't this belong to Documentation/config.txt instead, I wonder? ``` ## Michael Hendricks, 2007-05-17 14:35 Subject: Re: [PATCH] Document core.excludesfile for git-add Message-ID: <20070517143542.GB15709@ginosko.local> URL: https://gitlist.dev/e/20070517143542.GB15709%40ginosko.local In-Reply-To: <7vwsz89ftr.fsf@assigned-by-dhcp.cox.net> ``` On Wed, May 16, 2007 at 10:31:12PM -0700, Junio C Hamano wrote: > Thanks, but wouldn't this belong to Documentation/config.txt > instead, I wonder? It appears to my untrained eye that core.excludesfiles only works for git-add. It seems to have no effect on git-status and the only code that mentions core.excludesfile is builtin-add.c -- Michael ``` ## Petr Baudis, 2007-05-17 15:39 Subject: Re: [PATCH] Document core.excludesfile for git-add Message-ID: <20070517153921.GQ4489@pasky.or.cz> URL: https://gitlist.dev/e/20070517153921.GQ4489%40pasky.or.cz In-Reply-To: <20070517143542.GB15709@ginosko.local> ``` On Thu, May 17, 2007 at 04:35:44PM CEST, Michael Hendricks wrote: > On Wed, May 16, 2007 at 10:31:12PM -0700, Junio C Hamano wrote: > > Thanks, but wouldn't this belong to Documentation/config.txt > > instead, I wonder? > > It appears to my untrained eye that core.excludesfiles only works for > git-add. It seems to have no effect on git-status and the only code > that mentions core.excludesfile is builtin-add.c I believe the current policy should be that all config options are at least briefly listed in config.txt and possibly are described in more detail in the documentation of relevant command. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ Ever try. Ever fail. No matter. // Try again. Fail again. Fail better. -- Samuel Beckett ``` ## Johan Herland, 2007-05-17 15:45 Subject: Re: [PATCH] Document core.excludesfile for git-add Message-ID: <200705171745.09307.johan@herland.net> URL: https://gitlist.dev/e/200705171745.09307.johan%40herland.net In-Reply-To: <20070517143542.GB15709@ginosko.local> ``` On Thursday 17 May 2007, Michael Hendricks wrote: > On Wed, May 16, 2007 at 10:31:12PM -0700, Junio C Hamano wrote: > > Thanks, but wouldn't this belong to Documentation/config.txt > > instead, I wonder? > > It appears to my untrained eye that core.excludesfiles only works for > git-add. It seems to have no effect on git-status and the only code > that mentions core.excludesfile is builtin-add.c If so, we should probably fix that. The set of ignore files parsed by relevant git commands should be consistent. We don't want a situation where exclude patterns in a file are picked up by some git commands, but not by others. ...Johan -- Johan Herland, www.herland.net ```