Re: Fwd: Unexpected behavior of ls-files command when using --others --exclude-from, and a .gitignore file which resides in a subdirectory

From: Raúl Núñez de Arenas Coronado <raulnac@gmail.com>
Date: Jan 23, 2024, 06:08 UTC
Message-ID: <CAGF1KhWEnbOy1DQhv4xbov5Fg+hQdihWcwcT9A0f1b4Fc1gR-w@mail.gmail.com>
In-Reply-To: <xmqq5xzlrqoi.fsf@gitster.g>

Hi Junio!

El lun, 22 ene 2024 a las 22:42, Junio C Hamano (<gitster@pobox.com>) escribió:

Show 13 quoted lines

> We have been discussing to extend the mechanism so that we can have
> "precious" files, which also will be left out of the project (e.g.,
> "git add ." will not add to the index, just like an ignored file)
> but are not considered "expendable".  If file F is "precious":
>
>  - "git add ." will not add F to the index
>
>  - "git status" will not say F is left untracked and can be added
>
>  - "git clean -f" will not remove it.
>
>  - checking out a branch with a tracked file F/G will *fail*, to
>    prevent the loss of file.

And that is exactly the concept I'm handling here: files that should not be tracked BUT that are not expendable. You explained it concisely and perfectly :)))

I'll wait until that is implemented, and in the meantime I have a couple solutions I want to try, like using .gitprecious files and 'git ls-files --other --ignored --exclude-from=.gitprecious'. I have more ideas.

Thanks a lot for the help and the explanation!

-- 
Raúl Núñez de Arenas Coronado
.