mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: jw schultz <jw@pegasys.ws>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Hugo Mills <hugo-lkml@carfax.org.uk>
Subject: Re: [PATCH] More spelling fixes: loose->lose
Date: 01 Mar 2003 21:47:50 -0700	[thread overview]
Message-ID: <1046580472.2544.457.camel@spc1.mesatop.com> (raw)
In-Reply-To: <20030302031119.GB30797@pegasys.ws>

On Sat, 2003-03-01 at 20:11, jw schultz wrote:
> On Sat, Mar 01, 2003 at 08:28:07PM +0000, Hugo Mills wrote:
> >    Loose, pronounced with a soft "s", as in the word "spelling", means
> > badly-fitting or vague.
> 
> Actually it means "not tight" or unconstrained as in "loosen
> the collar and check airflow before performing
> mouth-to-mouth" or "let loose the dogs"
> 
> In actual usage loose and lose can be antonyms when
> referring to priveleges.  "loose privs" vs "lose privs".
> 
> I found at least one case of correction that looked wrong so
> i perused the lot, see comments.
> 
> > diff -ur linux-2.5.63-orig/arch/ia64/kernel/perfmon.c linux-2.5.63/arch/ia64/kernel/perfmon.c
> > --- linux-2.5.63-orig/arch/ia64/kernel/perfmon.c	2003-03-01 16:19:41.000000000 +0000
> > +++ linux-2.5.63/arch/ia64/kernel/perfmon.c	2003-03-01 19:55:03.000000000 +0000
> > @@ -2995,7 +2995,7 @@
> >  		 * interruptible). In this case, the PMU will be kept frozen and the process will 
> >  		 * run to completion without monitoring enabled.
> >  		 *
> > -		 * Of course, we cannot loose notify process when self-monitoring.
> > +		 * Of course, we cannot lose notify process when self-monitoring.
> 
> This might have been "loosely notify" but careful examination of the
> context idicates it should be "lose notification process" or
> "lose the notify process". 

In my patch to Linus five days ago which fixed most of the lose/loose
substitutions, I left this one in, guessing that it might mean "let
loose 'notify process'".  I was wrong, so that error remains in the
tree.  Reference changeset currently numbered 1.1035.  Good catch.

Steven


      reply	other threads:[~2003-03-02  4:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-01 20:28 Hugo Mills
2003-03-01 23:55 ` Steven Cole
2003-03-02  3:11 ` jw schultz
2003-03-02  4:47   ` Steven Cole [this message]

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=1046580472.2544.457.camel@spc1.mesatop.com \
    --to=elenstev@mesatop.com \
    --cc=hugo-lkml@carfax.org.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 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®