Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #70889 > unrolled thread
| Started by | "Rick C. Hodgin" <rick.c.hodgin@gmail.com> |
|---|---|
| First post | 2015-09-18 08:34 -0700 |
| Last post | 2015-10-06 12:46 -0700 |
| Articles | 12 on this page of 92 — 19 participants |
Back to article view | Back to comp.lang.c
Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-18 08:34 -0700
Re: Preparation for what's coming jacobnavia <jacob@jacob.remcomp.fr> - 2015-09-18 19:40 +0200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-18 10:52 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-18 12:48 -0700
Re: Preparation for what's coming Steven Hystad <steven.hystad@lunarinfrastructure.net> - 2015-09-22 19:22 -0600
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 13:09 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-19 13:13 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 13:48 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-19 14:19 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 14:50 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 14:56 -0700
Re: Preparation for what's coming jacobnavia <jacob@jacob.remcomp.fr> - 2015-09-20 00:11 +0200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 15:24 -0700
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-20 00:37 -0700
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-20 00:44 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-20 22:26 -0700
Re: Preparation for what's coming Keith Thompson <kst-u@mib.org> - 2015-09-21 08:31 -0700
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-09-22 10:38 +0200
Re: Preparation for what's coming gazelle@shell.xmission.com (Kenny McCormack) - 2015-09-22 08:44 +0000
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-09-22 10:59 +0200
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-22 02:50 -0700
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-22 03:09 -0700
Re: Preparation for what's coming Keith Thompson <kst-u@mib.org> - 2015-09-22 07:51 -0700
Re: Preparation for what's coming "James Harris" <james.harris.1@gmail.com> - 2015-09-22 20:34 +0100
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-09-23 10:17 +0200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-23 01:45 -0700
Re: Preparation for what's coming Keith Thompson <kst-u@mib.org> - 2015-09-23 08:50 -0700
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-23 11:10 -0700
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-09-24 16:11 +0200
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-24 08:17 -0700
Re: Preparation for what's coming James Kuyper <jameskuyper@verizon.net> - 2015-09-24 12:17 -0400
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-24 10:52 -0700
Re: Preparation for what's coming BruceS <bruces42@hotmail.com> - 2015-09-22 16:39 -0600
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-22 16:01 -0700
Re: Preparation for what's coming Ian Collins <ian-news@hotmail.com> - 2015-09-23 11:08 +1200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-22 16:30 -0700
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-09-23 10:38 +0200
Re: Preparation for what's coming Ian Collins <ian-news@hotmail.com> - 2015-09-23 21:32 +1200
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-23 03:04 -0700
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-09-23 13:10 +0200
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-21 11:55 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-19 15:27 -0700
Re: Preparation for what's coming Melzzzzz <mel@zzzzz.com> - 2015-09-20 01:02 +0200
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-19 17:13 -0700
Re: Preparation for what's coming Melzzzzz <mel@zzzzz.com> - 2015-09-20 02:28 +0200
Re: Preparation for what's coming Siri Cruz <chine.bleu@yahoo.com> - 2015-09-19 18:26 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-19 17:19 -0700
Re: Preparation for what's coming Keith Thompson <kst-u@mib.org> - 2015-09-19 16:28 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-19 17:23 -0700
Re: Preparation for what's coming Keith Thompson <kst-u@mib.org> - 2015-09-19 18:26 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 20:25 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 20:38 -0700
Re: Preparation for what's coming Ian Collins <ian-news@hotmail.com> - 2015-09-20 15:57 +1200
Re: Preparation for what's coming jacobnavia <jacob@jacob.remcomp.fr> - 2015-09-21 10:46 +0200
Re: Preparation for what's coming Jens Stuckelberger <Jens_Stuckelberger@nowhere.net> - 2015-09-20 23:37 +0000
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-21 13:04 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-21 13:19 -0700
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-21 14:12 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-21 14:22 -0700
Re: Preparation for what's coming Rosario19 <Ros@invalid.invalid> - 2015-09-22 00:37 +0200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-21 15:41 -0700
Re: Preparation for what's coming Rosario19 <Ros@invalid.invalid> - 2015-09-22 00:54 +0200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-21 16:03 -0700
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-22 03:09 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-22 03:49 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-22 04:12 -0700
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-22 04:14 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-22 04:45 -0700
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-23 12:24 -0700
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-23 13:16 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-24 11:25 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-22 12:44 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-06 06:21 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-06 07:55 -0700
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-10-06 09:09 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-06 09:14 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-06 09:16 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-10 21:26 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-10-10 23:45 -0700
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-10-11 00:31 -0700
Re: Preparation for what's coming Melzzzzz <mel@zzzzz.com> - 2015-10-11 13:36 +0200
Re: Preparation for what's coming Ian Collins <ian-news@hotmail.com> - 2015-10-11 21:35 +1300
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-11 06:10 -0700
Re: Preparation for what's coming Melzzzzz <mel@zzzzz.com> - 2015-10-11 15:38 +0200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-11 07:59 -0700
Re: Preparation for what's coming glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-10-06 21:05 +0000
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-10-07 00:59 -0700
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-10-07 11:43 +0200
VW (Re: Preparation for what's coming) Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-10-07 13:33 +0000
Re: VW (Re: Preparation for what's coming) glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-10-08 01:04 +0000
Re: Preparation for what's coming Ian Collins <ian-news@hotmail.com> - 2015-10-07 08:32 +1300
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-06 12:46 -0700
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
| From | Melzzzzz <mel@zzzzz.com> |
|---|---|
| Date | 2015-10-11 13:36 +0200 |
| Message-ID | <20151011133610.5c4376c2@maxa-pc> |
| In reply to | #72454 |
On Sat, 10 Oct 2015 23:45:23 -0700 "Chris M. Thomasson" <nospam@nospam.nospam> wrote: > > "Rick C. Hodgin" wrote in message > > news:3735071a-6cb2-4af3-b0a1-b7a08c715642@googlegroups.com... > > [...] > > > Why no rapture on Oct.06.2015 as people were again expecting? > > IIRC, the scripture basically says the real Jesus comes after a false > one with > supernatural power arrives. Jesus comes as a thief in the night... > > Trying to guess dates is fruitless? > Perhaps Jesus was alien? He will return in space ship ;)
[toc] | [prev] | [next] | [standalone]
| From | Ian Collins <ian-news@hotmail.com> |
|---|---|
| Date | 2015-10-11 21:35 +1300 |
| Message-ID | <d7ula7Fj978U5@mid.individual.net> |
| In reply to | #72453 |
Rick C. Hodgin wrote: > > Why no rapture on Oct.06.2015 as people were again expecting? The current series of Dr Who hasn't finished yet. -- Ian Collins
[toc] | [prev] | [next] | [standalone]
| From | "Rick C. Hodgin" <rick.c.hodgin@gmail.com> |
|---|---|
| Date | 2015-10-11 06:10 -0700 |
| Message-ID | <ad2da640-d69e-486c-a643-647d7b94845c@googlegroups.com> |
| In reply to | #72453 |
Jesus Himself is the third temple, and His believers are part of that temple. The temple is now built. And things are about to fundamentally change worldwide for the rest of man's time upon the Earth before the Lord's second coming, wherein He will destroy every enemy and establish His 1,000 year reign. Everything you think you've known about life, about this world, about your purpose for being alive, is about to be shaken, never to be the same again. The period of God's Grace against the evil goings on in this world is about to end. And then He will pour out His wrath upon all who are in rebellion against Him, and truth, embracing self and lies instead. The only shelter from the coming storm is in Jesus. He will forgive your sins if you believe, repent, ask forgiveness. He will change you so that you live your life for Him. Best regards, Rick C. Hodgin
[toc] | [prev] | [next] | [standalone]
| From | Melzzzzz <mel@zzzzz.com> |
|---|---|
| Date | 2015-10-11 15:38 +0200 |
| Message-ID | <20151011153840.065ddda3@maxa-pc> |
| In reply to | #72473 |
On Sun, 11 Oct 2015 06:10:34 -0700 (PDT) "Rick C. Hodgin" <rick.c.hodgin@gmail.com> wrote: > Jesus Himself is the third temple, and His believers > are part of that temple. > Rick stick, to the C...
[toc] | [prev] | [next] | [standalone]
| From | "Rick C. Hodgin" <rick.c.hodgin@gmail.com> |
|---|---|
| Date | 2015-10-11 07:59 -0700 |
| Message-ID | <76ec11c9-e333-4878-ae6e-4071e5c5a58a@googlegroups.com> |
| In reply to | #72476 |
Melzzzzz wrote: > Rick stick, to the C... https://www.youtube.com/watch?v=wJ81MZUlrDo "If you've just spent nearly 30 hours debugging some assembly... soon you'll be glad to write in C." Best regards, Rick C. Hodgin
[toc] | [prev] | [next] | [standalone]
| From | glen herrmannsfeldt <gah@ugcs.caltech.edu> |
|---|---|
| Date | 2015-10-06 21:05 +0000 |
| Message-ID | <mv1d3m$aeu$1@speranza.aioe.org> |
| In reply to | #72053 |
Malcolm McLean <malcolm.mclean5@btinternet.com> wrote: > On Tuesday, October 6, 2015 at 3:55:51 PM UTC+1, Rick C. Hodgin wrote: >> See an updated / expanded version located here: > The main headline on Sept 23 was a story about a car manufacturer > cheating on nitrous oxide emissions tests. It is on all oxides of nitrogen, not just nitrous oxide. Nitric oxide and nitrogen dioxide are important contributors to smog, and harmful to humans (and other animals and plants). > An important story, but hardly anything of shattering historical > importance. You were wrong. It does bring up some important points in regard to computer programming and liability. It isn't so obvious yet how high up it went, but there is pretty much no doubt that those writing the software knew what they were doing. Now, consider that such software engineers might want to get jobs somewhere else. Will you trust them with your project? -- glen
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.mclean5@btinternet.com> |
|---|---|
| Date | 2015-10-07 00:59 -0700 |
| Message-ID | <87a56761-7537-4e11-8622-11f81d9be768@googlegroups.com> |
| In reply to | #72086 |
On Tuesday, October 6, 2015 at 10:06:22 PM UTC+1, glen herrmannsfeldt wrote: > Malcolm McLean <malcolm.mclean5@btinternet.com> wrote: > > On Tuesday, October 6, 2015 at 3:55:51 PM UTC+1, Rick C. Hodgin wrote: > >> See an updated / expanded version located here: > > > The main headline on Sept 23 was a story about a car manufacturer > > cheating on nitrous oxide emissions tests. > > It is on all oxides of nitrogen, not just nitrous oxide. > Nitric oxide and nitrogen dioxide are important contributors > to smog, and harmful to humans (and other animals and plants). > > > An important story, but hardly anything of shattering historical > > importance. You were wrong. > > It does bring up some important points in regard to computer > programming and liability. It isn't so obvious yet how high > up it went, but there is pretty much no doubt that those > writing the software knew what they were doing. > > Now, consider that such software engineers might want to > get jobs somewhere else. Will you trust them with your project? > A dentist was recently caught doing unnecessary operations. Obviously another dentist had to be called into the court as an expert witness, and he confirmed that this is what he had done. The other dentist spoke of his shame and humiliation that another member of his profession would behave in such a fashion. But I don't feel the same way about the VW programmers. We don't really have the same concept of a code of ethics, we're not even a profession in the technical sense. (Microsoft-certified professional is an oxymoron, by the way, by definition a professional is certified by his professional body, of which he then becomes a member with a say over the certification process).
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2015-10-07 11:43 +0200 |
| Message-ID | <mv2pcq$bf$1@dont-email.me> |
| In reply to | #72086 |
On 06/10/15 23:05, glen herrmannsfeldt wrote:
> Malcolm McLean <malcolm.mclean5@btinternet.com> wrote:
>> On Tuesday, October 6, 2015 at 3:55:51 PM UTC+1, Rick C. Hodgin wrote:
>>> See an updated / expanded version located here:
>
>> The main headline on Sept 23 was a story about a car manufacturer
>> cheating on nitrous oxide emissions tests.
>
> It is on all oxides of nitrogen, not just nitrous oxide.
> Nitric oxide and nitrogen dioxide are important contributors
> to smog, and harmful to humans (and other animals and plants).
>
>> An important story, but hardly anything of shattering historical
>> importance. You were wrong.
>
> It does bring up some important points in regard to computer
> programming and liability. It isn't so obvious yet how high
> up it went, but there is pretty much no doubt that those
> writing the software knew what they were doing.
>
> Now, consider that such software engineers might want to
> get jobs somewhere else. Will you trust them with your project?
>
You can be sure that the software developers were doing what they were
told by the company (or department) leadership, not by their own
initiative. It is conceivable that they did not even know there was
cheating involved, if the tasks were divided up enough.
Such software cheats are not new (well, since this one apparently goes
back to at least 2008, it's not new either). For a while it was common
in graphics drivers - they detected that the user was running a known
benchmark program, and cheat in some way in order to give apparently
faster results. And it has been known for compiler developers to
"optimise" their tools for "special cases", such as SPEC_INT benchmarks.
And cheating, or law-breaking of various sorts, is certainly nothing new
amongst professionals. In some professions, such as the medical and
legal professions, you need to be licensed and the license involves
oaths against such unethical behaviour. This gives them extra
protection against being asked to do something questionable. But for
most people, there is no such thing. Your boss tells you to make the
changes, or be fired ("and you'll never work in this town again").
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2015-10-07 13:33 +0000 |
| Subject | VW (Re: Preparation for what's coming) |
| Message-ID | <slrnn1a7p6.5q5.grahn+nntp@frailea.sa.invalid> |
| In reply to | #72086 |
On Tue, 2015-10-06, glen herrmannsfeldt wrote: > Malcolm McLean <malcolm.mclean5@btinternet.com> wrote: >> On Tuesday, October 6, 2015 at 3:55:51 PM UTC+1, Rick C. Hodgin wrote: >>> See an updated / expanded version located here: > >> The main headline on Sept 23 was a story about a car manufacturer >> cheating on nitrous oxide emissions tests. ... > It does bring up some important points in regard to computer > programming and liability. It isn't so obvious yet how high > up it went, but there is pretty much no doubt that those > writing the software knew what they were doing. That's the part that fascinates me the most. How can you keep the lid on such a thing? I can't see how you can make it work. The core programmers in the engine area need to be in on it, and a whole management chain. And several layers of test and verification people. And maintenance and support. And anyone with read access to the source code. That's dozens of people already. You cannot keep QA out of the loop by sneaking it in very late, because while /some/ people are willing to cheat on emission benchmarks, fewer would do anything which is a safety problem, such as doing tests on anything but the software which reaches customers. It even complicates the recruitment process; you need to ask HR to hire only programmers with low moral standards. Or very naive programmers ... at any rate, precisely the people you /don't/ want to have for a lot of other reasons. Perhaps someone has done an analysis from this angle already ... /Jorgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | glen herrmannsfeldt <gah@ugcs.caltech.edu> |
|---|---|
| Date | 2015-10-08 01:04 +0000 |
| Subject | Re: VW (Re: Preparation for what's coming) |
| Message-ID | <mv4fej$524$1@speranza.aioe.org> |
| In reply to | #72135 |
Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: (snip) >>> The main headline on Sept 23 was a story about a car manufacturer >>> cheating on nitrous oxide emissions tests. As I noted before, it is other oxides than N2O. >> It does bring up some important points in regard to computer >> programming and liability. It isn't so obvious yet how high >> up it went, but there is pretty much no doubt that those >> writing the software knew what they were doing. > That's the part that fascinates me the most. How can you keep the lid > on such a thing? I can't see how you can make it work. Interesting question, maybe the answer will come out in the end. I am not sure which countries have such tests. It might be easier when the people involved don't work in the country doing the tests, but it would seem to me it can easily come out when someone gets fired. Unless they have a strong incentive (like a gun pointed at their head) not to tell, the secret can easily get out. > The core programmers in the engine area need to be in on it, and a > whole management chain. And several layers of test and verification > people. And maintenance and support. And anyone with read access to > the source code. That's dozens of people already. > You cannot keep QA out of the loop by sneaking it in very late, > because while /some/ people are willing to cheat on emission > benchmarks, fewer would do anything which is a safety problem, such > as doing tests on anything but the software which reaches customers. OK, say you have one persor responsible for taking the bits and writing them into ROMs. (And for now consider mask ROMs, though I don't know what they use.) If that person can do it just right, and avoid too many others from knowing, it might work. > It even complicates the recruitment process; you need to ask HR to > hire only programmers with low moral standards. Or very naive > programmers ... at any rate, precisely the people you /don't/ want to > have for a lot of other reasons. Seems that way to me. > Perhaps someone has done an analysis from this angle already ... Maybe the UWV group does that. It seems that they are funded by fines paid by previous violators of the testing laws. As I understand it, there were people wondering how VW managed to design an engine that didn't need urea injection, when all the others did. It wasn't that they were suspected of cheating, but what secret did they have for the low emissions. Then they started measuring while driving, and the secret started to come out. -- glen
[toc] | [prev] | [next] | [standalone]
| From | Ian Collins <ian-news@hotmail.com> |
|---|---|
| Date | 2015-10-07 08:32 +1300 |
| Message-ID | <d7ilumFectqU1@mid.individual.net> |
| In reply to | #72046 |
Rick C. Hodgin wrote: > See an updated / expanded version located here: > > http://www.libsf.org/rapture_puzzle/oct6/index.html $ date October 7, 2015 08:31:24 AM -- Ian Collins
[toc] | [prev] | [next] | [standalone]
| From | "Rick C. Hodgin" <rick.c.hodgin@gmail.com> |
|---|---|
| Date | 2015-10-06 12:46 -0700 |
| Message-ID | <60ca031c-964b-4158-9184-6c3fc44f0c75@googlegroups.com> |
| In reply to | #72080 |
On Tuesday, October 6, 2015 at 3:32:59 PM UTC-4, Ian Collins wrote:
> Rick C. Hodgin wrote:
> > See an updated / expanded version located here:
> >
> > http://www.libsf.org/rapture_puzzle/oct6/index.html
>
> $ date
> October 7, 2015 08:31:24 AM
> --
> Ian Collins
$ date
Tue Oct 6 15:41:00 EDT 2015
See:
http://whenisthenewmoon.com/
Yom Teruah: Sep.16.2015
Yom Kippur: Sep.25.2015
Sukkot: Sep.30.2015 thru Oct.06.2015
Last Great Day: Oct.07.2015
Most likely all relative to Jerusalem time, and to the Hebrew calendar
time of evening to evening, but nobody knows for sure until it happens.
Best regards,
Rick C. Hodgin
[toc] | [prev] | [standalone]
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
Back to top | Article view | comp.lang.c
csiph-web