From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] mpg132: bump to version 1.21.0
Date: Sun, 12 Oct 2014 01:20:59 +0300 [thread overview]
Message-ID: <20141011222059.GD3500@tarshish> (raw)
In-Reply-To: <5439ABF7.6050600@zacarias.com.ar>
Hi Gustavo,
On Sat, Oct 11, 2014 at 07:15:19PM -0300, Gustavo Zacarias wrote:
> On 10/11/2014 07:08 PM, Baruch Siach wrote:
> > Could not find these hashes there.
>
> Sourceforge trick: hit the 'i' button besides the file in question.
Thanks. Didn't know that. Maybe worth a mention in the comment.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-10-11 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 21:55 [Buildroot] [PATCH 1/2] file: bump to version 5.20 Gustavo Zacarias
2014-10-11 21:55 ` [Buildroot] [PATCH 2/2] mpg132: bump to version 1.21.0 Gustavo Zacarias
2014-10-11 22:08 ` Baruch Siach
2014-10-11 22:15 ` Gustavo Zacarias
2014-10-11 22:20 ` Baruch Siach [this message]
2014-10-12 7:15 ` Peter Korsgaard
2014-10-12 7:14 ` [Buildroot] [PATCH 1/2] file: bump to version 5.20 Peter Korsgaard
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=20141011222059.GD3500@tarshish \
--to=baruch@tkos.co.il \
--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