From: Herbert Poetzl <herbert@13thfloor.at>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] eliminate CLONE_* duplications
Date: Thu, 22 Sep 2005 01:58:10 +0200 [thread overview]
Message-ID: <20050921235810.GC18040@MAIL.13thfloor.at> (raw)
In-Reply-To: <Pine.LNX.4.61.0509211738160.3728@scrub.home>
On Wed, Sep 21, 2005 at 05:39:23PM +0200, Roman Zippel wrote:
> Hi,
>
> On Wed, 21 Sep 2005, Herbert Poetzl wrote:
>
> > well, I thought that is what my patch did, so please
> > could you elaborate on the 'properly' part, as this
> > might be the missing information here ...
>
> "It's more important to keep related definition together and
> organize them logically."
hmm, looks like we are dancing around in circles here
so please forgive my direct (and repeated) question:
_what_ do you consider 'logically organized' because
putting all the CLONE_* stuff into a separate file is
pretty logical for me ... but obviously not for you.
I have absolutely no problem with different, more
logical splitups, and I'm willing to break down the
entire sched.h if that will help the cause ... so
please enlighten me here ...
TIA,
Herbert
> bye, Roman
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2005-09-21 23:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 9:21 [Patch] eliminate CLONE_* duplications Herbert Poetzl
2005-09-21 10:55 ` Roman Zippel
2005-09-21 14:39 ` Herbert Poetzl
2005-09-21 14:53 ` Roman Zippel
2005-09-21 15:11 ` Herbert Poetzl
2005-09-21 15:39 ` Roman Zippel
2005-09-21 23:58 ` Herbert Poetzl [this message]
2005-09-27 15:25 ` Roman Zippel
2005-09-27 16:22 ` Herbert Poetzl
2005-09-27 17:04 ` Roman Zippel
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=20050921235810.GC18040@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).