From: Martin Dalecki <dalecki@evision-ventures.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: GPLONLY kernel symbols???
Date: Tue, 13 Nov 2001 11:48:51 +0100 [thread overview]
Message-ID: <3BF0FA93.54C056BF@evision-ventures.com> (raw)
In-Reply-To: <200111130324.fAD3OE916102@vindaloo.ras.ucalgary.ca> <Pine.GSO.4.21.0111122249160.22925-100000@weyl.math.psu.edu> <200111130358.fAD3wgb16617@vindaloo.ras.ucalgary.ca> <3BF09E44.58D138A6@mandrakesoft.com> <200111130437.fAD4b2j17329@vindaloo.ras.ucalgary.ca>
Richard Gooch wrote:
> If and when I step down as maintainer (if I do so, I'll publically
> pass the baton to the new maintainer), the new maintainer can indent
> to their preference. Until that time, *I'm* the maintainer, and *I*
> need to be able to read the code efficiently. It's the part of the
> kernel I spend the most time in, after all.
Or you could reindent to your style befor making changes
yourself as well. Consider this as an exercise in cooperation.
next prev parent reply other threads:[~2001-11-13 9:56 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 16:27 GPLONLY kernel symbols??? 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 ` Ben Greear
2001-10-17 20:18 ` pierre
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 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: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:15 ` Jeff Garzik
2001-11-13 4:37 ` Richard Gooch
2001-11-13 4:49 ` Alexander Viro
2001-11-13 5:03 ` Richard Gooch
2001-11-13 5:27 ` Alexander Viro
2001-11-13 5:35 ` Richard Gooch
2001-11-13 5:44 ` Jeff Garzik
2001-11-13 4:54 ` Jeff Garzik
2001-11-13 5:00 ` Richard Gooch
2001-11-13 5:14 ` Jeff Garzik
2001-11-13 5:23 ` Richard Gooch
2001-11-13 5:29 ` Robert Love
2001-11-13 5:44 ` Erik Andersen
2001-11-13 5:56 ` Richard Gooch
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 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 ` Martin Dalecki [this message]
2001-11-13 9:57 ` [OT] Coding Style (was: " Henning P. Schmiedehausen
2001-11-28 22:35 ` GPLONLY kernel symbols??? Dr. Kelsey Hudson
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=3BF0FA93.54C056BF@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=dalecki@evision.ag \
--cc=jgarzik@mandrakesoft.com \
--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