Josh Triplett <josh@xxxxxxxxxxxxxxxx> writes: > On Tue, Oct 10, 2023 at 10:02:20AM -0700, Junio C Hamano wrote: >> Sebastian Thiel <sebastian.thiel@xxxxxxxxxx> writes: >> >> > I'd like to propose adding a new standard gitattribute "precious". >> >> ;-). >> >> Over the years, I've seen many times scenarios that would have been >> helped if we had not just "tracked? ignored? unignored?" but also >> the fourth kind [*]. The word "ignored" (or "excluded") has always >> meant "not tracked, not to be tracked, and expendable" to Git, and >> "ignored but unexpendable" class was missing. I even used the term >> "precious" myself in those discussions. At the concept level, I >> support the effort 100%, but as always, the devil will be in the >> details. > > "I've already wanted this for years" is, honestly, the best response we > could *possibly* have hoped for. Yeah, but that is not what I gave here. It is something I saw people want from time to time over the years; I am not at all talking about my desire, or lack thereof, to add it to the system ;-) >> In previous discussions, nobody was disturbed that "git clean" was >> unaware of the "precious" class, but if we were to have the >> "precious" class in addition to "ignored" aka "expendable", I would >> not oppose to teach "git clean" about it, too. >> >> There was an early and rough design draft there in >> >> https://lore.kernel.org/git/7vipsnar23.fsf@xxxxxxxxxxxxxxxxxxxxxxxx/ >> >> which probably is worth a read, too. The project can say something like # force older git to ignore .config # older git unignores "$.config" without touching ".config" # but newer git applies the "last one wins" rule as usual # to mark ".config" as precious. !$.config if our syntax were to retrofit '!' prefix, and even more simply #:(precious) .config if we adopt Phillip's "comment abuse" idea, where older Git will treat it as saying ".config" is not to be added but is expendable, while newer Git will treat it as saying ".config" is not to be added and not to be clobbered.
