Attachment 39297 Details for Bug 30723 – Rename mpi file

[patch] Rename mpi file

0007-Rename-mpi-file-to-reflect-device-name-change.patch (text/plain), 1.48 KB, created by Jonathan Ernst on 2010-10-09 02:17:17 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Jonathan Ernst

Created: 2010-10-09 02:17:17 UTC

Size: 1.48 KB

patch

obsolete

>From 46da16db1a8f4bdfab83bac39f927b79cdfb3d26 Mon Sep 17 00:00:00 2001
>From: Jonathan Ernst <jonathan@ernstfamily.ch>
>Date: Sat, 9 Oct 2010 11:10:16 +0200
>Subject: Rename mpi file to reflect device name change
>
>---
> media-players/motorola-droid-milestone.mpi |   15 +++++++++++++++
> media-players/motorola-droid.mpi           |   15 ---------------
> 2 files changed, 15 insertions(+), 15 deletions(-)
> create mode 100644 media-players/motorola-droid-milestone.mpi
> delete mode 100644 media-players/motorola-droid.mpi
>
>diff --git a/media-players/motorola-droid-milestone.mpi b/media-players/motorola-droid-milestone.mpi
>new file mode 100644
>index 0000000..df07059
>--- /dev/null
>+++ b/media-players/motorola-droid-milestone.mpi
>@@ -0,0 +1,15 @@
>+[Device]
>+Vendor=Motorola
>+Product=Droid/Milestone
>+AccessProtocol=storage
>+DeviceMatch=usb:22b8:41d9;usb:22b8:41db;
>+Icon=phone-motorola-droid
>+
>+[Media]
>+OutputFormats=audio/mpeg;audio/aac;application/ogg
>+
>+[storage]
>+RequiresEject=true
>+AudioFolders=Music/
>+FolderDepth=4
>+
>diff --git a/media-players/motorola-droid.mpi b/media-players/motorola-droid.mpi
>deleted file mode 100644
>index df07059..0000000
>--- a/media-players/motorola-droid.mpi
>+++ /dev/null
>@@ -1,15 +0,0 @@
>-[Device]
>-Vendor=Motorola
>-Product=Droid/Milestone
>-AccessProtocol=storage
>-DeviceMatch=usb:22b8:41d9;usb:22b8:41db;
>-Icon=phone-motorola-droid
>-
>-[Media]
>-OutputFormats=audio/mpeg;audio/aac;application/ogg
>-
>-[storage]
>-RequiresEject=true
>-AudioFolders=Music/
>-FolderDepth=4
>-
>-- 
>1.7.1
>

Actions: View | Splinter Review

Attachments on bug 30723: 39296 | 39297

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.