Received-SPF: none
 receiver=logan.com; client-ip=216.148.227.85; envelope-from=jesse@jessfarr.com
Message-ID: <00e601c5de1f$9fb29300$057ba8c0@farr.com>
From: "jesse farr" <jesse@jessfarr.com>
To: "Rotary motors in aircraft" <flyrotary@lancaironline.net>
References: <list-800262@logan.com>
Subject: [FlyRotary] was Re: Shady Bend Report - 
Date: Mon, 31 Oct 2005 08:33:04 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit

Michael: Many prefer things just the way most email programs handle it; 
answer at the top, with >, or something like that, at the front of what is 
being replied to beneath. But, while I still prefer that way, I will have to 
admit as I get older, I can see the need for answering, then cutting and 
placing at the bottom like them lamar folks and some others seem to require. 
Remembering what the heck we are talking about and what all is covered is 
getting harder. <g> But, and, whatever, I just can not see for the very life 
of me why we have to keep stacking up longer and longer emails; but, then 
again, you have to dance to what those that throw the party play; so, if the 
list server owners/operators want it one way, I guess that is the way we 
need to do it at their party, anyway. It does help to be able to tell which 
is what, though. Didn't we have this discussion some time ago?
jofarr, soddy tn

----- Original Message ----- 
From: "Michael LaFleur" <mike.lafleur@sbcglobal.net>
>
> In the e-mail below, how am I supposed to determine
> which is the response? The only thing I can do is read
> the whole thing or ignore it. Most often I just ignore
> it and move on to the next message.