Back to bug 30088
Who | When | What | Removed | Added |
---|---|---|---|---|
vivek | 2010-10-05 06:59:56 UTC | Status | NEW | ASSIGNED |
Assignee | telepathy-bugs | vivek | ||
Summary | Implement Protocol.Interface.{Presence,Avatars}, so they can be undrafted. | Implement Protocol.Interface.Presence, so it can be undrafted. | ||
vivek | 2010-10-05 07:22:41 UTC | Blocks | 30085 | |
vivek | 2010-10-05 07:25:34 UTC | Keywords | patch | |
smcv | 2010-10-05 07:56:33 UTC | Whiteboard | review- | |
vivek | 2010-10-05 10:24:39 UTC | Whiteboard | review- | |
smcv | 2010-10-14 09:35:04 UTC | Blocks | 30087 | |
Depends on | 30087 | |||
Whiteboard | review+ when spec supports it | |||
smcv | 2010-10-25 12:25:23 UTC | Component | gabble | tp-doc |
Depends on | 30087 | 31102 | ||
Assignee | vivek | telepathy-bugs | ||
Summary | Implement Protocol.Interface.Presence, so it can be undrafted. | TpBaseProtocol: add Presence | ||
smcv | 2010-10-25 12:26:06 UTC | Component | tp-doc | tp-glib |
smcv | 2010-10-25 12:27:07 UTC | CC | vivek | |
smcv | 2010-10-25 12:28:54 UTC | Keywords | patch | |
URL | http://git.collabora.co.uk/?p=user/vivek/telepathy-glib;a=shortlog;h=refs/heads/ofdt-protocol-interface-presences | |||
Whiteboard | review+ when spec supports it | r+, but merge/rebase needed | ||
smcv | 2010-10-25 12:29:47 UTC | Blocks | 31106 | |
smcv | 2010-10-25 12:30:31 UTC | Blocks | 31107 | |
smcv | 2010-10-25 12:31:00 UTC | Blocks | 31108 | |
smcv | 2010-10-26 08:34:33 UTC | Keywords | patch | |
URL | http://git.collabora.co.uk/?p=user/vivek/telepathy-glib;a=shortlog;h=refs/heads/ofdt-protocol-interface-presences | http://git.collabora.co.uk/?p=user/smcv/telepathy-glib-smcv.git;a=shortlog;h=refs/heads/proto-presence | ||
Assignee | telepathy-bugs | simon.mcvittie | ||
Whiteboard | r+, but merge/rebase needed | |||
vivek | 2010-11-05 06:26:32 UTC | Whiteboard | review+ | |
smcv | 2010-11-05 06:47:56 UTC | Status | ASSIGNED | RESOLVED |
Resolution | --- | FIXED |
Back to bug 30088
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.