Mellotronists group photo

Yahoo Groups archive

Mellotronists

Index last updated: 2026-04-28 23:09 UTC

Message

Re: [Mellotronists] Re: Jon E. Salley

2010-10-13 by lsf5275@aol.com

Actually, I wondered why he wasn't on the list. Martin pointed out this sad 
 truth.
 
 
 
In a message dated 10/12/2010 11:37:57 P.M. Eastern Daylight Time,  
Mrarcoman@... writes:

Thanks Frank for bringing this up.  Whether you knew Jon or not (I  
remember his him, but didn't know him) - we should honor those who were one of  us!!
 
Hope to see you later Jon - Craig
 
 
In a message dated 10/12/2010 8:31:22 P.M. Pacific Daylight Time,  
jandjstrz@... writes:

 
 
 
 
Condolences. 
RIP 
 

-----Original  Message-----
From:  Mellotronists@yahoogroups.com [mailto:Mellotronists@yahoogroups.com] 
 On Behalf Of  lsf5275@...
Sent: Tuesday, October 12, 2010 9:36  PM
To:  newmellotrongroup@yahoogroups.com; Mellotronists@yahoogroups.com
Subject: [Mellotronists] Re: Jon E.  Salley 
 
 
 
 
For those of you  who, like me, have wondered about the absence of Jon 
Salley from these  groups, a little sleuthing by Martin Smith seems to have 
turned up the  unfortunate answer...
 

Jon E.  Salley
·          BORN: March 10,  1954  
·          DIED: May 14, 2010   
·          LOCATION: KS   
 
Sadly Jon has left  us. I recall that he was sick, but never considered the 
possibility that he  had died. I figured he got tired or bored. I for one 
will miss him  terribly. I can remember any number of great and amusing off 
list  exchanges over the years. He was one of my very first friends when I 
joined  the Mellotronists list many years back and he was a very funny guy. 
and also  very talented.
 

 
Jon had been  working on a new project, Tintagel. He has a web site, but it 
doesn't look  like he ever completed it. He also has his personal and 
Tintagel Myspace  pages. Go listen to his music. Pretty damn good. 
 

 
Frank

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.