From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Udev error and how to fix it.
Date: Thu, 18 Mar 2010 09:59:27 +0930 [thread overview]
Message-ID: <1268872167.6194.107.camel@localhost> (raw)
In-Reply-To: <20100317142552.GA9684@math.princeton.edu>
On Wed, 2010-03-17 at 10:25 -0400, Willie Wong wrote:
> On Wed, Mar 17, 2010 at 02:05:12PM +0100, Zeerak Mustafa Waseem wrote:
> > > I don't see any need for excuses, it sounds like fine common English to
> > > me, with the possible exception of a run-on "if".
I meant to use the word apology instead of excuse, but it was late for
me too :)
> > > The full sentence was "I usually always look to see if Dale has been
> > > involved in a thread if HAL is mentioned"
> > Ah it's just using two different words that describe seeing something :-)
> > I like to think that my english is a little better. I mean it should have been "see if" or "look to see whether" (as far as I remember anyway :-))
> >
> Huh, the "look to see" part, while inelegant and repetitive, is a common
> colloquialism, and I don't think was the problem. I was more thrown
> off by "usually always", which is either an oxymoron (if you take a
> strict view of the word "usually") or redundant (if you take "usually"
> to contain "always" as a subset). </pedant>
>
> (Looks like I only have off-topic contributions to this thread.)
me too.
"usually always" is also a colloquialism which means "almost always" ;)
ie. not quite always, but close to it... at least it usually always
means that.
But hey, if we were to be that picky on this list hardly anyone would be
here. That's why we have programming languages, because English is too
forgiving and fuzzy!
--
Iain Buchanan <iaindb at netspace dot net dot au>
War is like love, it always finds a way.
-- Bertolt Brecht, "Mother Courage"
next prev parent reply other threads:[~2010-03-18 0:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 8:42 [gentoo-user] Udev error and how to fix it Dale
2010-03-16 9:00 ` Dirk Uys
2010-03-16 9:15 ` Dale
2010-03-16 9:25 ` Neil Bothwick
2010-03-16 9:30 ` Dale
2010-03-16 9:48 ` Neil Bothwick
2010-03-16 9:59 ` Dale
2010-03-17 12:48 ` Iain Buchanan
2010-03-17 14:06 ` Dale
2010-03-16 17:39 ` James Ausmus
2010-03-16 19:29 ` Dale
2010-03-16 9:02 ` Neil Bothwick
2010-03-16 9:18 ` Dale
2010-03-16 10:13 ` Philip Webb
2010-03-16 10:31 ` Dale
2010-03-16 12:44 ` Neil Bothwick
2010-03-16 15:37 ` Zeerak Mustafa Waseem
2010-03-16 17:19 ` Willie Wong
2010-03-16 17:33 ` Zeerak Mustafa Waseem
2010-03-16 18:13 ` Dale
2010-03-16 18:38 ` Neil Bothwick
2010-03-16 19:25 ` Dale
2010-03-16 19:58 ` Neil Bothwick
2010-03-16 20:15 ` Dale
2010-03-16 21:28 ` Neil Bothwick
2010-03-16 21:42 ` Dale
2010-03-16 19:39 ` Alan McKinnon
2010-03-17 1:17 ` Peter Humphrey
2010-03-17 7:56 ` Zeerak Mustafa Waseem
2010-03-17 12:58 ` Iain Buchanan
2010-03-17 13:05 ` Zeerak Mustafa Waseem
2010-03-17 14:25 ` Willie Wong
2010-03-18 0:29 ` Iain Buchanan [this message]
2010-03-18 1:57 ` [gentoo-user] " walt
2010-03-18 9:52 ` Willie Wong
2010-03-18 16:58 ` Frank Steinmetzger
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=1268872167.6194.107.camel@localhost \
--to=iaindb@netspace.net.au \
--cc=gentoo-user@lists.gentoo.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