git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Denton Liu <liu.denton@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: "Martin Ågren" <martin.agren@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>
Subject: [PATCH v3 2/2] Docs: move core.excludesFile from git-add to gitignore
Date: Thu, 7 Mar 2019 00:25:30 -0800	[thread overview]
Message-ID: <f1bc7d5eb1ad15427f6d14c19c90595d09acabe5.1551947030.git.liu.denton@gmail.com> (raw)
In-Reply-To: <cover.1551947030.git.liu.denton@gmail.com>

There was a section on configuration mentioning core.excludesFile in
git-add.txt. However, the core.excludesFile config variable is not
exclusive to git-add. Move this description to gitignore.txt to be more
generic.
---
 Documentation/git-add.txt   | 9 ---------
 Documentation/gitignore.txt | 8 ++++++++
 2 files changed, 8 insertions(+), 9 deletions(-)

diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt
index 37bcab94d5..8b0e4c7fa8 100644
--- a/Documentation/git-add.txt
+++ b/Documentation/git-add.txt
@@ -193,15 +193,6 @@ for "git add --no-all <pathspec>...", i.e. ignored removed files.
 	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 linkgit:gitignore[5].
-
-
 EXAMPLES
 --------
 
diff --git a/Documentation/gitignore.txt b/Documentation/gitignore.txt
index 1c94f08ff4..b5bc9dbff0 100644
--- a/Documentation/gitignore.txt
+++ b/Documentation/gitignore.txt
@@ -132,6 +132,14 @@ full pathname may have special meaning:
  - Other consecutive asterisks are considered regular asterisks and
    will match according to the previous rules.
 
+CONFIGURATION
+-------------
+
+The optional configuration variable `core.excludesFile` indicates a path to a
+file containing patterns of file names to exclude, similar to
+`$GIT_DIR/info/exclude`.  Patterns in the exclude file are used in addition to
+those in `$GIT_DIR/info/exclude`.
+
 NOTES
 -----
 
-- 
2.21.0.368.gbf248417d7


  parent reply	other threads:[~2019-03-07  8:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 10:42 [PATCH 0/1] update git-clean.txt Denton Liu
2019-03-06 10:42 ` [PATCH 1/1] git-clean.txt: specify core.excludesFile variable is used Denton Liu
2019-03-06 20:22   ` Martin Ågren
2019-03-07  0:38     ` Junio C Hamano
2019-03-07  6:04 ` [PATCH v2 0/1] make git-clean.txt more precise Denton Liu
2019-03-07  6:05   ` [PATCH v2 1/1] git-clean.txt: clarify ignore pattern files Denton Liu
2019-03-07  6:56     ` Junio C Hamano
2019-03-07  7:37       ` Martin Ågren
2019-03-07  8:12         ` Junio C Hamano
2019-03-07  8:25   ` [PATCH v3 0/2] consolidate core.excludesFile docs Denton Liu
2019-03-07  8:25     ` [PATCH v3 1/2] git-clean.txt: clarify ignore pattern files Denton Liu
2019-03-07  8:25     ` Denton Liu [this message]
2019-03-08  0:17       ` [PATCH v3 2/2] Docs: move core.excludesFile from git-add to gitignore Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f1bc7d5eb1ad15427f6d14c19c90595d09acabe5.1551947030.git.liu.denton@gmail.com \
    --to=liu.denton@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=martin.agren@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).