mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Alexander Viro <viro@math.psu.edu>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: GPLONLY kernel symbols???
Date: Mon, 12 Nov 2001 22:35:20 -0700	[thread overview]
Message-ID: <200111130535.fAD5ZKa18694@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <Pine.GSO.4.21.0111130019340.22925-100000@weyl.math.psu.edu>
In-Reply-To: <200111130503.fAD53ns17951@vindaloo.ras.ucalgary.ca> <Pine.GSO.4.21.0111130019340.22925-100000@weyl.math.psu.edu>

Alexander Viro writes:
> 
> 
> On Mon, 12 Nov 2001, Richard Gooch wrote:
> 
> > Alexander Viro writes:
> > > No, you shouldn't.  For those of us who have similar problems with
> > > reviewing your code patch (later - CVS or RCS) will appear on
> > > ftp.math.psu.edu/pub/viro/ tommorrow.  End of story.
> > 
> > So is this the hostile takeover you've mentioned? Even though I'm
> > addressing the devfs races you've complained about so often, and have
> > been releasing these patches, you still wish to pursue this hostile
> > action?
> 
> Oh, for crying out loud!  You've very eloquently described the
> problems with reading code in alien style.  You have said that you
> were tired with other folks complaining about coding style of devfs.
> I replied telling these people where to look for a version that will
> be in standard kernel style, so that they could get off your back.
> What's your problem with _that_, for fsck sake?

Nothing at all, now that you've explained it. If all you want to do is
present the code I write in a form that's more convenient for others
to read, I think that's great.

I thought it might be the "hostile takeover" that you mentioned last
week, along with putting up a CVS tree. If that's not your intention,
that's fine. That's why I asked "is this the hostile takeover you've
mentioned", because I wasn't sure.

In fact, given the other code in the tree that doesn't conform to
CodingStyle, it makes sense run lindent on the whole tree and make
that available. As long as people understand that they should generate
patches against the real tree, and not the lindented one.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2001-11-13  5:36 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16 16:27 Christoph Lameter
2001-10-16 17:07 ` John Levon
2001-10-16 17:22   ` Alexander Viro
2001-10-17  2:17 ` Keith Owens
2001-10-17  4:59   ` Christoph Lameter
2001-10-17  5:54     ` Keith Owens
2001-10-17  6:15       ` Christoph Lameter
2001-10-17 18:28         ` Gerhard Mack
2001-10-17 19:34           ` Wayne Whitney
2001-10-17 21:31             ` pierre
2001-10-17 20:32               ` Arjan van de Ven
2001-10-17 19:14                 ` David Lang
2001-10-17 20:37                   ` Arjan van de Ven
2001-10-17 19:20                     ` David Lang
2001-10-17 22:02                 ` pierre
2001-10-18 13:45                   ` M. R. Brown
2001-10-21 16:05                   ` Alan Cox
2001-10-18 13:32               ` M. R. Brown
2001-10-17 19:34           ` Ben Greear
2001-10-17 20:18           ` pierre
2001-10-17 14:15   ` John Levon
2001-11-13  2:57   ` Richard Gooch
2001-11-13  3:21     ` Dave Jones
2001-11-13  3:24     ` Richard Gooch
2001-11-13  3:53       ` Alexander Viro
2001-11-13  3:58       ` Richard Gooch
2001-11-13  4:10         ` Alexander Viro
2001-11-13  4:15         ` Jeff Garzik
2001-11-13  9:57           ` [OT] Coding Style (was: Re: GPLONLY kernel symbols???) Henning P. Schmiedehausen
2001-11-28 22:35           ` GPLONLY kernel symbols??? Dr. Kelsey Hudson
2001-11-13  4:21         ` Richard Gooch
2001-11-13  4:36           ` Alexander Viro
2001-11-13  4:49           ` Richard Gooch
2001-11-13 10:46           ` Martin Dalecki
2001-11-13  4:37         ` Richard Gooch
2001-11-13  4:49           ` Alexander Viro
2001-11-13  4:54           ` Jeff Garzik
2001-11-13  4:58           ` Davide Libenzi
2001-11-13  5:07             ` John Alvord
2001-11-28 22:41               ` Dr. Kelsey Hudson
2001-11-29  0:35                 ` Michael H. Warfield
2001-11-29  5:04                   ` Dr. Kelsey Hudson
2001-11-13  5:00           ` Richard Gooch
2001-11-13  5:14             ` Jeff Garzik
2001-11-13  5:29               ` Robert Love
2001-11-13  5:23             ` Richard Gooch
2001-11-13  5:44               ` Erik Andersen
2001-11-13  5:56               ` Richard Gooch
2001-11-13  5:03           ` Richard Gooch
2001-11-13  5:27             ` Alexander Viro
2001-11-13  5:35             ` Richard Gooch [this message]
2001-11-13  5:44               ` Jeff Garzik
2001-11-13 10:01           ` Alan Cox
2001-11-13 10:29             ` Jeff Garzik
2001-11-13 13:47             ` Dave Jones
2001-11-13 16:54               ` Alan Cox
2001-11-13 17:17                 ` Dave Jones
2001-11-15 10:03               ` [PATCH] mtrr (was Re: GPLONLY kernel symbols???) Paul Gortmaker
2001-11-13 10:48           ` GPLONLY kernel symbols??? Martin Dalecki
2001-11-13  9:52         ` Roman Zippel
2001-11-13  4:05     ` Jeff Garzik

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=200111130535.fAD5ZKa18694@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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

all inboxes | Powered by JetHome®