Back to bug 19605
Who | When | What | Removed | Added |
---|---|---|---|---|
dafydd.harries | 2010-01-07 18:18:08 UTC | Status | NEW | ASSIGNED |
Summary | Gabble should cache disco responses | Gabble should cache client capabilities | ||
dafydd.harries | 2010-01-07 18:24:09 UTC | Assignee | telepathy | dafydd.harries |
URL | http://git.collabora.co.uk/?p=user/daf/telepathy-gabble;a=shortlog;h=refs/heads/caps-cache-0.8 | |||
Status | ASSIGNED | NEW | ||
Keywords | patch | |||
will | 2010-01-11 09:38:47 UTC | Keywords | patch | |
dafydd.harries | 2010-01-12 17:34:27 UTC | CC | will.thompson | |
dafydd.harries | 2010-01-13 10:52:06 UTC | Status | NEW | ASSIGNED |
will | 2010-01-19 10:59:04 UTC | Whiteboard | review+ | |
will | 2010-02-19 03:22:26 UTC | URL | http://git.collabora.co.uk/?p=user/daf/telepathy-gabble;a=shortlog;h=refs/heads/caps-cache-0.8 | http://git.collabora.co.uk/?p=user/daf/telepathy-gabble;a=shortlog;h=refs/heads/caps-cache-0.9 |
Whiteboard | review+ | review- | ||
smcv | 2010-02-24 08:20:45 UTC | URL | http://git.collabora.co.uk/?p=user/daf/telepathy-gabble;a=shortlog;h=refs/heads/caps-cache-0.9 | http://git.collabora.co.uk/?p=user/smcv/telepathy-gabble-smcv.git;a=shortlog;h=refs/heads/caps-cache |
Keywords | patch | |||
QA Contact | telepathy-bugs | |||
Whiteboard | review- | |||
will | 2010-03-26 09:16:46 UTC | Assignee | dafydd.harries | will.thompson |
Status | ASSIGNED | NEW | ||
will | 2010-03-26 11:16:00 UTC | Assignee | will.thompson | telepathy-bugs |
URL | http://git.collabora.co.uk/?p=user/smcv/telepathy-gabble-smcv.git;a=shortlog;h=refs/heads/caps-cache | http://git.collabora.co.uk/?p=user/wjt/telepathy-gabble-wjt.git;a=shortlog;h=refs/heads/caps-cache-0.9 | ||
smcv | 2010-04-12 08:00:08 UTC | Whiteboard | review+ | |
smcv | 2010-05-17 07:57:19 UTC | Status | NEW | ASSIGNED |
Assignee | telepathy-bugs | will.thompson | ||
will | 2010-05-21 04:31:44 UTC | Status | ASSIGNED | RESOLVED |
Resolution | --- | FIXED |
Back to bug 19605
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.