public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] size-in-bytes
Date: Sun, 17 Feb 2002 00:10:35 +0100	[thread overview]
Message-ID: <3C6EE6EB.9070506@evision-ventures.com> (raw)
In-Reply-To: <UTC200202162245.WAA31932.aeb@cwi.nl>

Andries.Brouwer@cwi.nl wrote:

>I planned a road to happiness in 92 steps, where each of the steps
>
Beware I may drive you to ruin if there will be less or more then 92 ;-)...

>does something clear and simple, simplifies the tree, beautifies
>the code, restructures in a clearly necessary way.
>Indeed, your suggested steps are also there.
>Five or six of these steps found their way into the kernel,
>(some thanks to Christoph Hellwig) but there is still a long way to go.
>The present patch is just a rediff of step 02.
>
My main concern is simple the following: The broken design was there for 
already 8 years and
the cleanup just goes far too slow for my personal taste if it goes at 
the same peace of speed as
of now...

>I do not know what the best strategy is, these times.
>I see you and Vojtech do good things to the IDE code,
>but would myself prefer to do such things in a series
>of really small steps. That way it is also very clear
>for Andre what happens.
>
Well I have no problems to synchronize in small steps. However I have
problems with synchronization in microsteps, becouse due to my daily 
dueties, which btw.
have *nothing* with kernel hacking to do, I can hardly go below the
resolution of a day.... Or more precisely: some time at afternoon which 
can vary
between:
- nothing
- a whole night
- a whole weekend

depending on:
- my personal mood,
- my druglevel,
- blood preassure,
- my world domination dreams (Andre thinks so apparently :-),
- the current conjugation between saturn and venus,

and so on...

But in fact: I'm flexible and even more happy if somebody, who can 
certainly devote more
time to it then me, just picks the shit^Wsuggestions I call patches up...

In regards of Andre, well unfortunately, after reading his last mail 
about my employer and
what-a-not, well I  have some... please  excuse me... concerns about his 
mind-wellth ;-)



  reply	other threads:[~2002-02-16 23:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-16 22:45 [PATCH] size-in-bytes Andries.Brouwer
2002-02-16 23:10 ` Martin Dalecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-21  9:54 Andries.Brouwer
2002-02-18 23:29 Andries.Brouwer
2002-02-18 23:38 ` Daniel Phillips
2002-02-16 21:41 Andries.Brouwer
2002-02-16 22:05 ` Martin Dalecki
2002-02-16 16:09 Andries.Brouwer
2002-02-16 21:09 ` Martin Dalecki
2002-02-18 22:43 ` Daniel Phillips
2002-02-21  7:04   ` Benjamin LaHaise

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=3C6EE6EB.9070506@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=Andries.Brouwer@cwi.nl \
    --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