From: Rusty Russell <rusty@rustcorp.com.au>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Generated files destruction
Date: Fri, 13 Sep 2002 10:42:08 +1000 [thread overview]
Message-ID: <20020913015502.29C4E2C08B@lists.samba.org> (raw)
In-Reply-To: Your message of "Thu, 12 Sep 2002 15:53:45 EST." <Pine.LNX.4.44.0209121551010.31494-100000@chaos.physics.uiowa.edu>
In message <Pine.LNX.4.44.0209121551010.31494-100000@chaos.physics.uiowa.edu> y
ou write:
> On Thu, 12 Sep 2002, Rusty Russell wrote:
>
> > I would like to start migrating all build-generated files to
> > names matching "generated*" or ".generated*", esp. those which look
> > like source files. This is mainly for readability and for simplicity
> > when diffing built kernel trees. I'll be encouraging various
> > maintainers who generate (.c, .h and .s) files which are not meant to
> > be shipped with the kernel source to migrate, in my copious free
> > time...
>
> I think the proper solution here is actually separate obj/src dirs,
> instead of special names. It's actually quite easy to get that implemented
> in the current kbuild, I just didn't find the time for proper testing yet.
> I'll have a patch ready for testing soon, though.
Sure, if it basically comes for free. Otherwise, I don't see any
attraction in separating them: cp -al linux-2.5.34 working-2.5.34-foo
takes a couple of seconds.
Cheers!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-09-13 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 7:13 [PATCH] Generated files destruction Rusty Russell
2002-09-12 20:53 ` Kai Germaschewski
2002-09-13 0:42 ` Rusty Russell [this message]
2002-09-30 16:23 ` Linus Torvalds
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=20020913015502.29C4E2C08B@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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