From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] mplayer: bump to v1.0rc2
Date: Thu, 5 Feb 2009 17:10:34 +0100 [thread overview]
Message-ID: <20090205171034.341e8a1c@hcegtvedt> (raw)
Hi
The attached patch bumps mplayer to v1.0rc2. I am unsure if any of the
following patches needs to be converted as well:
mplayer-1.0rc1-largefile.patch
mplayer-1.0rc1-ppc-configure.patch
mplayer-1.0rc1-remove-sys-timeb.patch
The other patches in SVN are not needed for v1.0rc2. This patch also
contains the Atmel vendor patch to give a boost on AVR32 devices.
--
Best regards,
Hans-Christian Egtvedt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mplayer-bump-v1.0rc2.patch
Type: text/x-patch
Size: 218159 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090205/85e4438e/attachment-0001.bin>
next reply other threads:[~2009-02-05 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 16:10 Hans-Christian Egtvedt [this message]
2009-02-13 19:39 ` [Buildroot] [patch] mplayer: bump to v1.0rc2 Peter Korsgaard
2009-02-13 20:26 ` Markus Heidelberg
2009-02-18 14:32 ` Hans-Christian Egtvedt
2009-02-18 14:34 ` Hans-Christian Egtvedt
2009-02-18 14:36 ` Peter Korsgaard
2009-02-13 20:23 ` Markus Heidelberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090205171034.341e8a1c@hcegtvedt \
--to=hans-christian.egtvedt@atmel.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox