From: Junio C Hamano <gitster@pobox.com>
To: Sebastian Thiel <sebastian.thiel@icloud.com>
Cc: Elijah Newren <newren@gmail.com>,
Elijah Newren via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Josh Triplett <josh@joshtriplett.org>,
Phillip Wood <phillip.wood123@gmail.com>
Subject: Re: [PATCH] precious-files.txt: new document proposing new precious file type
Date: Fri, 19 Jan 2024 10:45:50 -0800 [thread overview]
Message-ID: <xmqqy1cljh5t.fsf@gitster.g> (raw)
In-Reply-To: <4421D442-1BB2-4C89-834F-9E70F4CF360B@icloud.com> (Sebastian Thiel's message of "Fri, 19 Jan 2024 08:51:26 +0100")
Sebastian Thiel <sebastian.thiel@icloud.com> writes:
> I am glad I can pull my initial proposition of 'having both syntaxes' off
> the table to side with this version - it's gorgeous.
>
> It's easy to forget that the search-order when matching ignore patterns
> is back to front, which makes this 'trick' work.
The true gem is not the search-order, though. It is the "last one
wins" rule. Back to front search is merely an implementation detail
to optimize the search so that we can stop at the first hit ;-)
> If the insights gained with the last couple of emails would see their digest
> in the user-facing documentation, I think precious files wouldn't only become
> usable but would also allow projects to make the their choice during
> the transition period during which some users will inevitably access the repository
> with a Git that doesn't know about precious files yet.
OK.
next prev parent reply other threads:[~2024-01-19 18:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 2:25 [PATCH] precious-files.txt: new document proposing new precious file type Elijah Newren via GitGitGadget
2023-12-27 5:28 ` Junio C Hamano
2023-12-27 6:54 ` Elijah Newren
2023-12-27 22:15 ` Junio C Hamano
2024-01-18 7:51 ` Sebastian Thiel
2024-01-18 19:14 ` Junio C Hamano
2024-01-18 21:33 ` Sebastian Thiel
2024-01-19 2:37 ` Elijah Newren
2024-01-19 7:51 ` Sebastian Thiel
2024-01-19 18:45 ` Junio C Hamano [this message]
2024-01-19 2:58 ` Elijah Newren
2024-01-19 16:53 ` Phillip Wood
2024-01-19 17:17 ` Junio C Hamano
2024-01-24 6:50 ` Elijah Newren
2024-02-11 22:08 ` Sebastian Thiel
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=xmqqy1cljh5t.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=josh@joshtriplett.org \
--cc=newren@gmail.com \
--cc=phillip.wood123@gmail.com \
--cc=sebastian.thiel@icloud.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.
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).