Back to bug 28199
Who | When | What | Removed | Added |
---|---|---|---|---|
smcv | 2010-05-21 04:39:30 UTC | Depends on | 28200 | |
smcv | 2010-06-02 11:15:46 UTC | Depends on | 28201 | |
smcv | 2010-06-16 10:57:02 UTC | Keywords | patch | |
Status | NEW | ASSIGNED | ||
URL | http://git.collabora.co.uk/?p=user/smcv/telepathy-gabble-smcv.git;a=shortlog;h=refs/heads/roster-assumptions | |||
smcv | 2010-06-25 06:19:10 UTC | URL | http://git.collabora.co.uk/?p=user/smcv/telepathy-gabble-smcv.git;a=shortlog;h=refs/heads/roster-assumptions | http://git.collabora.co.uk/?p=user/smcv/telepathy-gabble-smcv.git;a=shortlog;h=refs/heads/contact-list |
smcv | 2010-07-28 11:08:20 UTC | Keywords | patch | |
smcv | 2010-08-03 08:18:09 UTC | Keywords | patch | |
Summary | port Gabble to TpContactListManager/TpBaseContactList | port Gabble to TpBaseContactList | ||
smcv | 2010-08-26 05:54:17 UTC | Keywords | patch | |
smcv | 2010-08-26 06:54:44 UTC | Keywords | patch | |
URL | http://git.collabora.co.uk/?p=user/smcv/telepathy-gabble-smcv.git;a=shortlog;h=refs/heads/contact-list | http://git.collabora.co.uk/?p=user/smcv/telepathy-gabble-smcv.git;a=shortlog;h=refs/heads/contact-list-fixes | ||
david.laban | 2010-09-20 06:47:51 UTC | CC | david.laban | |
smcv | 2010-09-21 03:55:35 UTC | Keywords | patch | |
URL | http://git.collabora.co.uk/?p=user/smcv/telepathy-gabble-smcv.git;a=shortlog;h=refs/heads/contact-list-fixes | http://git.collabora.co.uk/?p=user/smcv/telepathy-gabble-smcv.git;a=shortlog;h=refs/heads/contact-list-reviewed | ||
smcv | 2010-10-01 06:48:46 UTC | URL | http://git.collabora.co.uk/?p=user/smcv/telepathy-gabble-smcv.git;a=shortlog;h=refs/heads/contact-list-reviewed | http://git.collabora.co.uk/?p=user/smcv/telepathy-gabble-smcv.git;a=shortlog;h=refs/heads/really-enum |
CC | guillaume.desmottes | |||
smcv | 2010-10-01 06:48:58 UTC | Keywords | patch | |
smcv | 2010-10-05 09:32:54 UTC | Status | ASSIGNED | RESOLVED |
Resolution | --- | FIXED |
Back to bug 28199
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.