Skip to contentSkip to conversation

.gitignore files really necessary?

DISCUSSION Coywolf Qi Hunt 3 participants 5 messages Jan 6, 2006

lore
Share & tools
lore
#0 lore raw

Hello,

I see you keep updating .gitignore files. That would be a never ending extra burden IMHO. May I suggest we all use KBUILD_OUTPUT instead to keep the source tree clean? Or am I missing you?

Coywolf

#1 lore raw
Quoted 7 lines · Coywolf Qi Hunt

Hello,

I see you keep updating .gitignore files. That would be a never ending extra burden IMHO. May I suggest we all use KBUILD_OUTPUT instead to keep the source tree clean? Or am I missing you?

Coywolf

Seperate output dirs are nice for building release kernels, but for doing development it makes things more difficult. The .gitignore files don't affect the actual build, so it doesn't matter much if they arent't totally kept up to date.

--
Brian Gerst

#2 lore raw
Quoted 11 lines · Brian Gerst
Quoted 7 lines · Coywolf Qi Hunt

Hello,

I see you keep updating .gitignore files. That would be a never ending extra burden IMHO. May I suggest we all use KBUILD_OUTPUT instead to keep the source tree clean? Or am I missing you?

Coywolf

Seperate output dirs are nice for building release kernels, but for doing development it makes things more difficult. The .gitignore files

How? An example? I think it firstly benefits development, like making diffs.

Quoted 2 lines

don't affect the actual build, so it doesn't matter much if they arent't totally kept up to date.

But someone has to maintain them.

Coywolf

#3 lore raw
Quoted 8 lines · Coywolf Qi Hunt
Quoted 7 lines · Brian Gerst
Quoted 6 lines · Coywolf Qi Hunt

Hello,

I see you keep updating .gitignore files. That would be a never ending extra burden IMHO. May I suggest we all use KBUILD_OUTPUT instead to keep the source tree clean? Or am I missing you?

Quoted 5 lines
Quoted 3 lines
Quoted 1 line

Coywolf

Seperate output dirs are nice for building release kernels, but for doing development it makes things more difficult. The .gitignore files

How? An example? I think it firstly benefits development, like making diffs.

Making diffs is what git is for.

--
Brian Gerst

#4 lore raw
In reply to Coywolf Qi Hunt
Quoted 5 lines · Coywolf Qi Hunt

Hello,

I see you keep updating .gitignore files. That would be a never ending extra burden IMHO. May I suggest we all use KBUILD_OUTPUT instead to keep the source tree clean? Or am I missing you?

You will see a number of .gitignore updates until we get the kernel covered as is. After that the .gitignore files will seldom see updates.

Also some of the patches even change things already to simplify stuff. Look at last patch from Brian that ignores *.so in all the trees - this covers all the architectures using vdso tricks.

And the typical developer does not want to use KBUILD_OUTPUT, that would be cumbersome when debugging the kernel - so requesting all users to start using KBUILD_OUTPUT (make O=...) is not an option.

Sam