Are you talking about the reply text being at the top of the email
rather than the bottom? I think it makes it more readable with the reply
at the top. In fact, I sometimes don't read the mailing list posts that
have the reply at the bottom because then I have to scroll all the way
down, whereas top posted is immediately readable as soon as I click on
the message. Sounds like I'm just being lazy but when there are 30 other
things going on I just don't have time to do that.Plus it makes it MUCH
harder to read on a mobile device with the reply on the bottom (at least
in my case).
Just my 2 cents. Wasn't my intention to derail the thread but I had to
say it.
Josh Patten
Assistant Network Administrator
Brazos County IT Dept.
(979) 361-4676
On 3/24/2010 6:00 PM, mkitchin.pub...@gmail.com wrote:
That is why I was a little surprised to see that it was fixed. I
didn't think any progress had been made. (Sorry for top posting -
bberry doesn't format well)
Sent via BlackBerry from T-Mobile
------------------------------------------------------------------------
*From: * Tony Graziano <tgrazi...@myitdepartment.net>
*Date: *Wed, 24 Mar 2010 18:29:59 -0400
*To: *Matthew Kitchin (public/usenet)<mkitchin.pub...@gmail.com>
*Cc: *Scott Lawrence<xmlsc...@gmail.com>; <sipx-users@list.sipfoundry.org>
*Subject: *Re: [sipx-users] 4.1.7
On Wed, Mar 24, 2010 at 6:24 PM, Matthew Kitchin (public/usenet)
<mkitchin.pub...@gmail.com <mailto:mkitchin.pub...@gmail.com>> wrote:
On 3/24/2010 5:18 PM, Scott Lawrence wrote:
> On Wed, 2010-03-24 at 17:02 -0500, Matthew Kitchin (public/usenet)
> wrote:
>
>> On 3/24/2010 3:37 PM, Tony Graziano wrote:
>>
>>> Only been up for a couple of days but definitely quashed my
zombie (FS
>>> CPU) with it.
>>>
>> This issue is definitely fixed in the latest version? I haven't
seen any
>> updates on the open ticket. that will be a blessing for me when
I am
>> able to upgrade to a version where this issue is resolved.
>>
> Queries as to the state of issues are much easier to respond to when
> they actually cite the issue id or url.
>
> In general, the issue status is the tracker is as up to date as
> possible. Depending on circumstances (especially when the
developer has
> not been able to reliably reproduce the reported symptom),
marking an
> issue Resolved may be deferred until after the original reporter has
> been able to verify the fix, but in any event comments in the issue
> should reflect what is known at any one time.
>
>
>
Sorry. http://track.sipfoundry.org/browse/XX-7751
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
<mailto:sipx-users@list.sipfoundry.org>
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
The problem with that ticket is that the root cause was never found. I
submitted multiple snapshots of the ailing system I had, rebuilt the
system from scratch, then finally updated it to 4.1.7 a couple of days
ago on a separate system (backup/install on new system/restore/upgrade).
I submitted backtraces as well. I never got the feeling the cause was
ever discovered and provided everything that was asked for.
**
Tony
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
