lyskomd-qa January 2003

lyskomd-qa@lists.lysator.liu.se

1 participants
54 discussions

[Bug 957] Call to get server time zone
by bugzilla-daemon＠cvs.lysator.liu.se 04 Jan '03

04 Jan '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=957 byers(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |292 nThis| | ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 957] New: Call to get server time zone
by bugzilla-daemon＠cvs.lysator.liu.se 04 Jan '03

04 Jan '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=957 Summary: Call to get server time zone Product: lyskomd Version: 2.0.7 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: server AssignedTo: ceder(a)lysator.liu.se ReportedBy: byers(a)lysator.liu.se QAContact: lyskomd-qa(a)lists.lysator.liu.se Since timestamps in the LysKOM protocol are relative the server timezone, it should be possible to query the server for its timezone. I propose the following call: @node get-timezone @section get-timezeone [111] (Recommended) @findex set-timezone @example set-timezone [111] ( ) -> ( @lt{INT23} ); @end example This call returns the server timezone expressed as seconds west of the international date line (which can also be viewed as seconds west of GMT plus 43200). The offset is relative the international date line rather than GMT since the LysKOM protocol does not support signed integers. @subheading Error codes This call always succeeds. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 877] mark-as-read uses mark_conference_as_changed, not mark_person_as_changed
by bugzilla-daemon＠cvs.lysator.liu.se 01 Jan '03

01 Jan '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=877 ------- Additional Comments From ceder(a)lysator.liu.se 2003-01-01 12:12 ------- Yes, this is likely the root cause for these problems. However, I want to reproduce the bug in the test suite before I fix it. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 877] mark-as-read uses mark_conference_as_changed, not mark_person_as_changed
by bugzilla-daemon＠cvs.lysator.liu.se 01 Jan '03

01 Jan '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=877 ------- Additional Comments From byers(a)lysator.liu.se 2003-01-01 04:03 ------- Could be the root cause of some of the "text added to conference not marked as read" problems reported on lyskom-elisp-client (i.e. bug 212)? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

lyskomd-qa January 2003