From: Dmitry Gutov <dgutov@yandex.ru>
To: jan.synacek@posteo.org
Cc: 55632@debbugs.gnu.org, DG <raaahh@gmail.com>
Subject: bug#55632: [PATCH] Add new user option project-vc-find-tracked-only
Date: Wed, 1 Jun 2022 01:49:08 +0300 [thread overview]
Message-ID: <437b78f7-f4a9-670d-9b74-69ae8a565767@yandex.ru> (raw)
In-Reply-To: <43b5eada954e592cc0c747368a3dbdb7@posteo.de>
On 30.05.2022 14:00, jan.synacek@posteo.org wrote:
> Thank you for the review. I addressed your comments in the new version
> of the patch.
Thanks.
One last thing here. The manual addition says:
+Also, some VC back-ends consider ``untracked'' files by default.
+That behavior is controllable with the variable
+@code{project-vc-include-untracked}.
Should that say "some Project back-ends ..."? Or better yet, "the VC
Project back-end". Because that's the only one in the core that has any
notion of "untracked files".
And that behavior is so for all VC backends, with Git and Hg simply
having custom file listing code (for better performance). The rest
delegate to 'find', only picking up the list of ignores (like bzrignore,
svnignore, etc).
Consequently, the new variable will only affect the VC Project backend's
behavior only with Hg and Git.
next prev parent reply other threads:[~2022-05-31 22:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 9:08 bug#55632: [PATCH] Add new user option project-vc-find-tracked-only Jan Synáček
2022-05-27 11:01 ` Lars Ingebrigtsen
2022-05-27 13:55 ` Dmitry Gutov
2022-05-29 21:41 ` Dmitry Gutov
2022-05-30 11:00 ` jan.synacek
2022-05-31 22:49 ` Dmitry Gutov [this message]
2022-06-02 19:01 ` jan.synacek
2022-06-02 19:19 ` Eli Zaretskii
2022-06-02 23:45 ` Dmitry Gutov
2022-06-03 5:44 ` Eli Zaretskii
2022-06-04 0:37 ` Dmitry Gutov
2022-06-04 6:29 ` Eli Zaretskii
2022-06-04 9:40 ` Dmitry Gutov
2022-05-30 10:08 ` jan.synacek
2022-05-31 22:57 ` Dmitry Gutov
2022-06-01 15:21 ` jan.synacek
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=437b78f7-f4a9-670d-9b74-69ae8a565767@yandex.ru \
--to=dgutov@yandex.ru \
--cc=55632@debbugs.gnu.org \
--cc=jan.synacek@posteo.org \
--cc=raaahh@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.