From: Brian Gerst <bgerst@didntduck.org>
To: Coywolf Qi Hunt <qiyong@fc-cn.com>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: .gitignore files really necessary?
Date: Fri, 06 Jan 2006 08:10:28 -0500 [thread overview]
Message-ID: <43BE6C44.6040504@didntduck.org> (raw)
In-Reply-To: <20060106055845.GA12015@localhost.localdomain>
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
next prev parent reply other threads:[~2006-01-06 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 2:25 .gitignore files really necessary? Coywolf Qi Hunt
2006-01-06 3:42 ` Brian Gerst
2006-01-06 5:58 ` Coywolf Qi Hunt
2006-01-06 13:10 ` Brian Gerst [this message]
2006-01-06 15:41 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43BE6C44.6040504@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiyong@fc-cn.com \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox