public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Next cut of new devfs core
Date: Wed, 14 Nov 2001 02:21:48 +0100	[thread overview]
Message-ID: <3BF1C72C.2B5B5EB3@linux-m68k.org> (raw)
In-Reply-To: <200111131855.fADIt2Q26535@vindaloo.ras.ucalgary.ca>

Richard Gooch wrote:

> If people could try this out and report back, I'd appreciate it.

Do you have any other intentions for us than to just "try this out"? If
not then an URL to the patch would suffice instead of flooding the list
with lots of 80kB patches.
If you want other feedback, I would greatly appreciated it, if you would
make it a bit easier for other developers. Incremental patches would
help to see what actually changed, or even better make them available
through CVS (I think I suggested that before).
Your coding style was already mentioned as well, so I'm not going to
repeat that. Anyway, an important point you should understand is that,
you might be the devfs maintainer, but devfs is not an isolated project.
The common project is Linux, which is maintained by lots of people, to
make such a cooperative development effort possible these people have to
agree on some basic rules. One of these rules is the coding style, Linus
might not care too much about it, but by now you should have noticed
several other developers do.
To maintain a high code quality a constant code review is necessary, a
single person can mistakes, that's normal, but it's important to learn
from mistakes. That also requires that other people are able review the
code, but you aren't making it very easy to review your code. If you're
going to continue with this attitude I can only support Al to split the
code. Sorry, there isn't much room for an ego trip, if you're not able
to deliver high quality code (for whatever reasons of which we got
enough by now).

bye, Roman


  parent reply	other threads:[~2001-11-14  1:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 18:55 [PATCH] Next cut of new devfs core Richard Gooch
2001-11-13 19:06 ` Benjamin LaHaise
2001-11-14  1:21 ` Roman Zippel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-13  1:21 Richard Gooch
2001-11-09  7:51 Richard Gooch
2001-11-08 19:55 Richard Gooch
2001-11-07 19:22 Richard Gooch
2001-11-06 20:11 Richard Gooch

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=3BF1C72C.2B5B5EB3@linux-m68k.org \
    --to=zippel@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    /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