| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The usual approvers/observers logic is followed, to preserve as much
normal channel behaviour as possible.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This allows internally generated requests which require external
interaction to be atomic from the point of view of the caller,
and prevents MC and "real" handlers from treadin on one-another's
toes.
|
|
|
|
|
| |
These requests will typically be handled by MC itself rather than being
dispatched to a "real" handler.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
git+ssh://git.freedesktop.org/git/telepathy/telepathy-mission-control
|
|
|
|
| |
Makes MC master actually compilable!
|