From: Junio C Hamano <gitster@pobox.com>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: Denton Liu <liu.denton@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
"Robert P. J. Day" <rpjday@crashcourse.ca>
Subject: Re: [PATCH 1/1] git-clean.txt: specify core.excludesFile variable is used
Date: Thu, 07 Mar 2019 09:38:20 +0900 [thread overview]
Message-ID: <xmqqmum7o6wz.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAN0heSqTCQaTgWq4+-dxP0DFjtL=syq_W=T0cb66-2YPB4Tc-w@mail.gmail.com> ("Martin Ågren"'s message of "Wed, 6 Mar 2019 21:22:01 +0100")
Martin Ågren <martin.agren@gmail.com> writes:
> But on the topic of preferring shorter, I sort of wonder if we really
> need to provide all of those filenames here. The point we're trying to
> make is that we consider another source. So something like this would be
> just as technically correct, I think:
>
> Use the given exclude pattern in addition to those found in .gitignore
> and similar files (see linkgit:gitignore[5]).
Yes. Unless we devise some mechanism to prevent these text that
list the places exclusion list are read from spread across the
documentation set, saying "found in usual places (see $there)" and
making sure we have the authoritative single place up-to-date is a
good approach.
next prev parent reply other threads:[~2019-03-07 0:38 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 [this message]
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 ` [PATCH v3 2/2] Docs: move core.excludesFile from git-add to gitignore Denton Liu
2019-03-08 0:17 ` 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=xmqqmum7o6wz.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=liu.denton@gmail.com \
--cc=martin.agren@gmail.com \
--cc=rpjday@crashcourse.ca \
/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).