Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.acorn.misc > #3392
| From | M Harding <riscos@mdharding.org.uk> |
|---|---|
| Subject | Re: Getting close to raspberry pi time |
| Newsgroups | comp.sys.acorn.misc |
| Date | 2012-01-21 20:22 +0000 |
| Message-ID | <5255314fcdriscos@mdharding.org.uk> (permalink) |
| References | (9 earlier) <gemini.4f15fe6c00ad7bed02d0%nwsgrp@ntlworld.com> <525369f5benoise@audiomisc.co.uk> <gemini.4f16bdfb00084a6f0310%nwsgrp@ntlworld.com> <52538cf2cdnoise@audiomisc.co.uk> <525524d590see.sig@walkingingermany.invalid> |
| Organization | None |
In article <525524d590see.sig@walkingingermany.invalid>, Russell Hafter News <see.sig@walkingingermany.invalid> wrote: > In article <52538cf2cdnoise@audiomisc.co.uk>, Jim Lesurf > <noise@audiomisc.co.uk> wrote: > > When I used to lecture courses for a living <sic?> I once > > or twice was told off by colleages for using technical > > terms like "buggered" for equipment that was, erm, > > toes-up. (The students never complained.) To me, it was > > normal engineering parlance. > I understand that the correct term in certain dialects of > pidgin is 'all buggered up'. > At least, so I was told by a catholic missionary (male) who > had been seriously shocked immediately on arrival at a > nunnery in New Guinea to hear one nun telling another that > the sewing machine was 'all buggered up'. I am only shocked that he was shocked. But then, my family background is mechanical engineering. It's British Standard Technical English, I'd have thought - and concur that "up" is the version I've always been accustomed to. Michael Harding Rev. Preb. M.D. Harding riscos@mdharding.org.uk
Back to comp.sys.acorn.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Getting close to raspberry pi time Folderol <folderol@ukfsn.org> - 2012-01-11 21:39 +0000
Re: Getting close to raspberry pi time Martin Hansen <mhh@shrewsbury.org.uk> - 2012-01-12 01:11 -0800
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-12 15:26 +0000
Re: Getting close to raspberry pi time Chris Evans <chris@cjemicros.co.uk> - 2012-01-12 16:03 +0000
Re: Getting close to raspberry pi time Mark Beerling <invalid@online.de> - 2012-01-12 17:57 +0100
Re: Getting close to raspberry pi time Tim Hill <tim@invalid.org.uk> - 2012-01-14 17:37 +0000
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-14 21:02 +0000
Re: Getting close to raspberry pi time Rick Murray <heyrickmail-usenet@yahoo.co.uk> - 2012-01-15 02:51 +0100
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-15 02:44 +0000
Re: Getting close to raspberry pi time Rick Murray <heyrickmail-usenet@yahoo.co.uk> - 2012-01-15 15:45 +0100
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-15 17:48 +0000
Re: Getting close to raspberry pi time Rick Murray <heyrickmail-usenet@yahoo.co.uk> - 2012-01-16 06:24 +0100
Re: Getting close to raspberry pi time Russell Hafter News <see.sig@walkingingermany.invalid> - 2012-01-16 08:43 +0000
Re: Getting close to raspberry pi time Rick Murray <heyrickmail-usenet@yahoo.co.uk> - 2012-01-16 19:48 +0100
Re: Getting close to raspberry pi time Russell Hafter News <see.sig@walkingingermany.invalid> - 2012-01-16 19:52 +0000
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-16 20:37 +0000
Re: Getting close to raspberry pi time Rick Murray <heyrickmail-usenet@yahoo.co.uk> - 2012-01-17 07:38 +0100
Re: Getting close to raspberry pi time Dave Symes <dave@triffid.co.uk> - 2012-01-17 08:33 +0000
Re: Getting close to raspberry pi time Russell Hafter News <see.sig@walkingingermany.invalid> - 2012-01-17 10:20 +0000
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-17 11:47 +0000
Re: Getting close to raspberry pi time Dave Higton <davehigton@dsl.pipex.com> - 2012-01-17 20:11 +0000
Re: Getting close to raspberry pi time Dave Symes <dave@triffid.co.uk> - 2012-01-17 21:17 +0000
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-17 23:10 +0000
Re: Getting close to raspberry pi time Russell Hafter News <see.sig@walkingingermany.invalid> - 2012-01-17 10:23 +0000
Re: Getting close to raspberry pi time Fred Bambrough <fred@[127.0.0.1]> - 2012-01-17 11:32 +0000
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-17 11:52 +0000
Re: Getting close to raspberry pi time M Harding <riscos@mdharding.org.uk> - 2012-01-17 12:18 +0000
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-17 22:54 +0000
Re: Getting close to raspberry pi time M Harding <riscos@mdharding.org.uk> - 2012-01-18 10:16 +0000
Re: Getting close to raspberry pi time Bryn Evans <d@a.invalid> - 2012-01-18 14:42 +0000
Re: Getting close to raspberry pi time Jim Lesurf <noise@audiomisc.co.uk> - 2012-01-17 12:31 +0000
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-17 23:04 +0000
Re: Getting close to raspberry pi time Jim Lesurf <noise@audiomisc.co.uk> - 2012-01-18 09:28 +0000
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-18 12:41 +0000
Re: Getting close to raspberry pi time Jim Lesurf <noise@audiomisc.co.uk> - 2012-01-18 15:50 +0000
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-18 21:10 +0000
Re: Getting close to raspberry pi time SG nws <nwsgrp@ntlworld.com> - 2012-01-18 23:54 +0000
Re: Getting close to raspberry pi time Russell Hafter News <see.sig@walkingingermany.invalid> - 2012-01-21 18:05 +0000
Re: Getting close to raspberry pi time (OT) Peter Young <pnyoung@ormail.co.uk> - 2012-01-21 18:55 +0000
Re: Getting close to raspberry pi time M Harding <riscos@mdharding.org.uk> - 2012-01-21 20:22 +0000
Re: Getting close to raspberry pi time "Ste (news)" <steve@revi11.plus.com> - 2012-01-14 17:42 +0000
csiph-web