From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: Shaun Case <warmsocks@gmail.com>,
Elijah Newren <newren@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Possible regression for sparse-checkout in git 2.27.0
Date: Thu, 04 Jun 2020 17:56:37 -0700 [thread overview]
Message-ID: <xmqqtuzqnxdm.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <0aab7056-7176-01bc-ca7b-01356cbace4c@gmail.com> (Derrick Stolee's message of "Thu, 4 Jun 2020 20:32:42 -0400")
Derrick Stolee <stolee@gmail.com> writes:
> The first is due to the .gitignore syntax. The syntax allows exact
> matches for _directories_ using a trailing slash "/". For example,
> we can match everything in A/B/C with the pattern
>
> A/B/C/
>
> This would match the files in A/B/C/ and its subdirectories, but will
> not match a file A/B/C.txt or A/B/C1/. There is no equivalent matching
> for files, so A/B/C _will_ match a file A/B/C and A/B/C.txt. Whether this
> matters to you or not depends on your file structure.
The pattern A/B/C _will_ match a file A/B/C and a directory A/B/C/,
but I do not think it matches a file A/B/C.txt (or a path with any
other suffix).
I suspect that for the purpose of your explanation, the pattern
A/B/C does not have to match A/B/C.txt to cause trouble; the fact
that it matches directory A/B/C would be sufficient, I guess.
next prev parent reply other threads:[~2020-06-05 0:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 1:08 Possible regression for sparse-checkout in git 2.27.0 Shaun Case
2020-06-03 4:37 ` Elijah Newren
2020-06-03 15:36 ` Derrick Stolee
2020-06-04 7:27 ` Elijah Newren
2020-06-04 20:50 ` Shaun Case
2020-06-05 0:32 ` Derrick Stolee
2020-06-05 0:56 ` Junio C Hamano [this message]
2020-06-05 13:07 ` Derrick Stolee
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=xmqqtuzqnxdm.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=stolee@gmail.com \
--cc=warmsocks@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).