Bug 28222 - sync with hal-info
Summary: sync with hal-info
Status: RESOLVED FIXED
Alias: None
Product: media-player-info
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Martin Pitt
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-23 11:25 UTC by Paul Menzel
Modified: 2010-05-25 07:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
2nd patch: Add comment about »;«. (1.08 KB, application/octet-stream)
2010-05-23 11:26 UTC, Paul Menzel 		Details
Show Obsolete (1) View All

Description Paul Menzel 2010-05-23 11:25:36 UTC 
I am not sure if I cloned the correct branch. I took the one mentioned on [2]. The site is down right now, but cgit.freedesktop.org still worked. Maybe you should mention the official repository also in the README.

I am not sure about the second fix. Discard it if it is wrong.

It would be great if you could extent the README to cover the storage section or point to some resource.

And unrelated to this bug, I just want to inform you that there were some updates in hal-info regarding media players.

[1] http://people.freedesktop.org/~teuf/media-player-info
[2] http://packages.debian.org/sid/media-player-info
Comment 1 Paul Menzel 2010-05-23 11:26:48 UTC 
Created attachment 35806 [details]
2nd patch: Add comment about »;«.
Comment 2 Martin Pitt 2010-05-25 07:45:25 UTC 
Comment on attachment 35806 [details]
2nd patch: Add comment about »;«.

Thanks Paul, but the current README already points out the semi-colons.

This is the official branch now:

http://cgit.freedesktop.org/media-player-info/
Comment 3 Martin Pitt 2010-05-25 07:45:44 UTC 
So I'm devoting this bug for syncing with hal-info.
Comment 4 Martin Pitt 2010-05-25 07:54:25 UTC 
There was just one new music player in hal-info, we already had the others.

http://cgit.freedesktop.org/media-player-info/commit/?id=a21e57ccce0a3aea4d3062bd6ca41f643ef8ea74

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.