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 22, 2024, 21:07 UTC
Message-ID: <CAGF1KhU=o2rb-tCjZAG278kgoW50NYymsJakUwiMxWTQ33gQYA@mail.gmail.com>
In-Reply-To: <xmqqfryprsyp.fsf@gitster.g>

Hi Junio, and thanks a lot for your reply :)

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

Show 13 quoted lines

> Raúl Núñez de Arenas Coronado <raulnac@gmail.com> writes:
>
> > In short: using 'git ls-files --others
> > --exclude-from=subdir/.gitignore' results in an empty listing if
> > subdir/.gitignore contains '*". IMHO that pattern should be applied to
> > the subdir contents ...
>
> I do not think so.
>
> Imagine what would happen then if you did
>
>     $ cp subdir/.gitignore /var/tmp/1
>     $ git ls-files --others --exclude-from=/var/tmp/1

I understand this use case, yes. I was thinking about what git itself does when ignoring files, especially when dealing with .gitgnore files in subdirectories, but clearly this needs a different policy, yes.

What I needed from this command is a way of backing up some ignored files. These files should not go into the repository, but I'm using them temporarily for development so it is a good idea to back them up. I'll just backup the entire repository instead, is not a big deal :))

Again, thanks for your reply and your explanation! It's a huge honor to be replied to by no less than the Git team leather!

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