Merge lp://staging/~mhr3/dockmanager/metadata-update into lp://staging/dockmanager
Proposed by
Michal Hruby
Status: | Merged |
---|---|
Merged at revision: | 32 |
Proposed branch: | lp://staging/~mhr3/dockmanager/metadata-update |
Merge into: | lp://staging/dockmanager |
Diff against target: |
497 lines (+260/-74) 16 files modified
configure.ac (+4/-5) daemon/dockmanager-daemon.vala (+188/-15) metadata/banshee_control.py.info (+5/-4) metadata/deluge_badge.py.info (+5/-4) metadata/emesene_control.py.info (+5/-4) metadata/gajim_badge.py.info (+5/-4) metadata/gtg_menus.py.info (+5/-4) metadata/liferea_badge.py.info (+5/-4) metadata/open_terminal_here.py.info (+5/-4) metadata/pidgin_control.py.info (+5/-4) metadata/rhythmbox_control.py.info (+5/-4) metadata/tomboy_menus.py.info (+5/-4) metadata/transmission_badge.py.info (+5/-4) metadata/tsclient_menus.py.info (+5/-4) metadata/zeitgeist_journal.py.info (+4/-3) metadata/zeitgeist_menus.py.info (+4/-3) |
To merge this branch: | bzr merge lp://staging/~mhr3/dockmanager/metadata-update |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robert Dyer (community) | Needs Fixing | ||
Review via email:
|
To post a comment you must log in.
First of all, your diff includes way more than what you wanted. You should fix that up.
Second, what is the point to the metadata changes? What is the format used? Is it just a true INI file format? Must we verify the section is named 'DEFAULT'? What if it isnt, do we still use it? Will we allow other sections, if so what are those?