Re: What's cooking in git.git (Apr 2019, #01; Thu, 4)
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Apr 4, 2019, 21:29 UTC
- Message-ID
- <xmqqmul5e9y0.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <CACsJy8CmkFNv7Fy+rSY0Q=1DhYSrpSfU=XEpSS6QRLASJtsVew@mail.gmail.com>
Duy Nguyen <pclouds@gmail.com> writes:
Show 13 quoted lines
> On Thu, Apr 4, 2019 at 5:29 PM Junio C Hamano <gitster@pobox.com> wrote: >> * nd/precious (2019-04-01) 1 commit >> - Introduce "precious" file concept >> >> "git clean" learned to pay attention to the 'precious' attributes >> and keep untracked paths with the attribute instead of removing. >> >> Will merge to 'next'. > > There was no conclusion from the last thread if I remember correctly > and I kind of gave up on it. If you want to include anyway, should we > go for a more specific attribute (e.g. "clean") and leave "precious" > for later whenever it's better defined?
I'd rather pick between (1) using the final name for the concept we want to eventually achieve, i.e. "precious", and starting small, i.e. "initially, only git-clean knows about it", or (2) doing nothing. Per-command 'precious-this', 'precious-that' that would be left as interface wart for years is not a pretty sight I want to see.