public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Werner Almesberger <wa@almesberger.net>
Cc: Dave Jones <davej@codemonkey.org.uk>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Benjamin LaHaise <bcrl@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Those ruddy punctuation fixes
Date: Fri, 07 Mar 2003 17:09:29 -0800	[thread overview]
Message-ID: <3E6942C9.1040204@kegel.com> (raw)
In-Reply-To: <20030307212925.S2791@almesberger.net>

Werner Almesberger wrote:
> One problem with spelling fixes is that there's never a good
> moment, nor a good procedure to do them.
> 
> 
>>There are _dozens_ of known problems, and I'll take patches
>>fixing real problems over spelling fixes any day.
> 
> 
> I guess it would be nice if Linus would give some advance warning
> when he's going to accept speelnig fixes. That way, people with
> "real work" could schedule a few weeks at the beach, while the
> spelling police does its grisly job.
> 
> Of course, we all know that this will never happen ;-)

The next best thing might be for the spelling police
to maintain an archive of all the accepted spellfix patches.
That would let a sufficiently motivated person
(say, a spelling policeman) to offer a patch update
service with a reasonable certainty that he could
bring arbitrary patches up to date with respect to
the spellfixes in the main tree.
I've outlined a proposal for this at http://www.kegel.com/kerspell

This spellfix business is way more work than is reasonable.
The people who spend the time making it work while taking
care of all these issues (avoiding pun removal, avoiding
breakage, avoiding wrong corrections, patch updating)
are clearly on acid, but I salute them.  Me, I just take
notes and watch :-)
- Dan

-- 
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045


  reply	other threads:[~2003-03-08  0:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07  7:16 Those ruddy punctuation fixes Dan Kegel
2003-03-07 17:17 ` Benjamin LaHaise
2003-03-07 18:00   ` Dan Kegel
2003-03-07 23:15   ` Alan Cox
2003-03-08  0:52     ` Dave Jones
2003-03-08  0:04       ` Randy.Dunlap
2003-03-08  0:29       ` Werner Almesberger
2003-03-08  1:09         ` Dan Kegel [this message]
2003-03-08  2:18           ` Werner Almesberger
2003-03-08  1:08       ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-03-05 11:10 Russell King
2003-03-05 11:22 ` John Bradford
2003-03-05 14:18   ` Mike Dresser
2003-03-06  1:50   ` jw schultz
2003-03-06  9:58     ` Russell King
2003-03-06 10:46     ` John Bradford
2003-03-05 12:20 ` Dave Jones
2003-03-06  3:11   ` Steven Cole
2003-03-07  1:04     ` Val Henson
2003-03-07  2:44       ` Steven Cole
2003-03-07  3:33         ` Martin J. Bligh
2003-03-07  4:02           ` Steven Cole
2003-03-07  5:11             ` Martin J. Bligh
2003-03-07 17:04             ` Hans Reiser
     [not found]     ` <mailman.1047000901.5238.linux-kernel2news@redhat.com>
2003-03-07  3:07       ` Pete Zaitcev

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=3E6942C9.1040204@kegel.com \
    --to=dank@kegel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bcrl@redhat.com \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wa@almesberger.net \
    /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