git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Git Mailing list <git@vger.kernel.org>
Subject: does "git clean" deliberately ignore "core.excludesFile"?
Date: Sat, 23 Feb 2019 10:11:53 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.21.1902231008530.28936@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]


  not sure why i never noticed this before, but the "-x" option for
"git clean" reads:

 -x
     Don’t use the standard ignore rules read from .gitignore
     (per directory) and $GIT_DIR/info/exclude, but do still use
     the ignore rules given with -e options. This allows
     removing all untracked files, including build products.
     This can be used (possibly in conjunction with git reset)
     to create a pristine working directory to test a clean
     build.

  but i see no mention of whether the file specified by
core.excludesFile is taken into account, and perusing the source code
doesn't seem to show that command checking that config option.

  am i misreading something? and if not, is there a reason git clean
does not consult core.excludesFile?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                  http://crashcourse.ca/dokuwiki

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

             reply	other threads:[~2019-02-23 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23 15:11 Robert P. J. Day [this message]
2019-02-23 15:28 ` does "git clean" deliberately ignore "core.excludesFile"? Junio C Hamano
2019-02-23 18:06   ` Johannes Schindelin
2019-02-23 18:19     ` Johannes Schindelin
2019-02-23 18:32       ` Robert P. J. Day
2019-02-24  5:30         ` Junio C Hamano
2019-02-24 14:15           ` Johannes Schindelin

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=alpine.LFD.2.21.1902231008530.28936@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --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).