Jeremy Huddleston Sequoia <jeremyhu@xxxxxxxxx> writes:
> This was causing problems with ppc/sha1ppc.S
"causing problems"? How? The source file is already tracked so
"git add" to record updates to it would work just fine, and "git
status" would report "modified" for it, with or without "*.S" in the
.gitignore file, no?
To emulate, I just added ".*S" to .gitignore and modified
ppc/sha1ppc.S to double check whta happens.
We still have the build rule for %.s in our Makefile, so ignoring
".s" is still the right thing to do to make sure "git add dir/"
won't add "dir/frotz.s" by accident. I sense the downside of doing
so outweighs whatever benefit it would have on case incapable
filesystems (and it is unclear what problem this change is trying to
work around).
> Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@xxxxxxxxx>
> ---
> .gitignore | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.gitignore b/.gitignore
> index 0d77ea5894..a5db584576 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -195,7 +195,7 @@
> *.deb
> /git.spec
> *.exe
> -*.[aos]
> +*.[ao]
> *.py[co]
> .depend/
> *.gcda
