From: Jon Tibble <meths@btinternet.com>
To: Peter Hicks <Peter.Hicks@POGGS.CO.UK>
Cc: jw schultz <jw@pegasys.ws>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: Trivial, pedantic spelling mistakes for 2.4.21-rc2
Date: 12 May 2003 00:28:00 +0100 [thread overview]
Message-ID: <1052695680.4770.3.camel@hyperion.rift> (raw)
In-Reply-To: <3EBE2D24.1030208@POGGS.CO.UK>
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
On Sun, 2003-05-11 at 11:59, Peter Hicks wrote:
> jw schultz wrote:
>
> >>Your mailer ate it. Wordwrap, tab2space and unchanged lines
> >>are missing a leading space.
> >>
> >>
> I give up, I'm going home!
>
> http://journal.poggs.com/2003/05/10/spell-2.4.21rc2.patch
>
> Its definitely there. Intact. Untouched by Mozilla.
>
Yep, it was there.
The following patch applies on top to fix FIMXME
Jon.
[-- Attachment #2: spell_FIXME.patch --]
[-- Type: text/x-patch, Size: 655 bytes --]
diff -uar linux-2.4.21-rc2/drivers/scsi/cpqfcTSstructs.h linux-2.4.21-rc2-devel/drivers/scsi/cpqfcTSstructs.h
--- linux-2.4.21-rc2/drivers/scsi/cpqfcTSstructs.h Sun May 11 20:12:38 2003
+++ linux-2.4.21-rc2-devel/drivers/scsi/cpqfcTSstructs.h Sun May 11 20:13:13 2003
@@ -93,7 +93,7 @@
#define CPQFCTS_CMD_PER_LUN 15 // power of 2 -1, must be >0
#define CPQFCTS_REQ_QUEUE_LEN (TACH_SEST_LEN/2) // must be < TACH_SEST_LEN
-/* FIMXME - these are crap too */
+/* FIXME - these are crap too */
#define LinuxVersionCode(v, p, s) (((v)<<16)+((p)<<8)+(s))
#ifndef DECLARE_MUTEX_LOCKED
#define DECLARE_MUTEX_LOCKED(sem) struct semaphore sem = MUTEX_LOCKED
next prev parent reply other threads:[~2003-05-11 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3EBDAB7F.4000905@wanadoo.es>
2003-05-11 10:21 ` PATCH: Trivial, pedantic spelling mistakes for 2.4.21-rc2 Peter Hicks
[not found] ` <20030511104229.GE16654@pegasys.ws>
2003-05-11 10:59 ` Peter Hicks
2003-05-11 23:28 ` Jon Tibble [this message]
2003-05-10 14:23 Peter Hicks
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=1052695680.4770.3.camel@hyperion.rift \
--to=meths@btinternet.com \
--cc=Peter.Hicks@POGGS.CO.UK \
--cc=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.