.gitignore files really necessary?

.gitignore files really necessary?

[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

Re: .gitignore files really necessary?

[Brian Gerst]

Coywolf Qi Hunt wrote:
> 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

Re: .gitignore files really necessary?

[Coywolf Qi Hunt]

On Thu, Jan 05, 2006 at 10:42:21PM -0500, Brian Gerst wrote:
> Coywolf Qi Hunt wrote:
> > 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.

> 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

Re: .gitignore files really necessary?

[Brian Gerst]

Coywolf Qi Hunt wrote:
> On Thu, Jan 05, 2006 at 10:42:21PM -0500, Brian Gerst wrote:
>> Coywolf Qi Hunt wrote:
>>> 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.

Making diffs is what git is for.

--
				Brian Gerst

Re: .gitignore files really necessary?

[Sam Ravnborg]

On Fri, Jan 06, 2006 at 10:25:31AM +0800, Coywolf Qi Hunt wrote:
> 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