From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/3] package/spandsp: bump version to 3.0.0
Date: Sat, 29 Aug 2020 22:56:02 +0200 [thread overview]
Message-ID: <20200829225602.14aa4647@windsurf.home> (raw)
In-Reply-To: <20200829204005.2815997-1-bernd.kuhls@t-online.de>
On Sat, 29 Aug 2020 22:40:03 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Reformatted hashes.
>
> Switched upstream to freeswitch repo which is maintained by the author
> of spandsp:
> https://github.com/signalwire/freeswitch/issues/681#issuecomment-671498542
>
> The previous project URL http://www.soft-switch.org/ is not reachable
> anymore.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
I've applied to next, but I have two comments/questions.
> +SPANDSP_VERSION = 3.0.0-6ec23e5a7e
This version naming scheme is weird. Why not just 3.0.0 ? What is even
more weird is that https://files.freeswitch.org/downloads/libs/ shows
two 3.0.0 versions:
spandsp-3.0.0-6ec23e5a7e.tar.gz
spandsp-3.0.0-f995f452ee.tar.gz
Another thing: could you update on release-monitoring.org the
definition of this project at
https://release-monitoring.org/project/12600/ to properly track this
new upstream location ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-08-29 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 20:40 [Buildroot] [PATCH/next 1/3] package/spandsp: bump version to 3.0.0 Bernd Kuhls
2020-08-29 20:40 ` [Buildroot] [PATCH/next 2/3] package/sofia-sip: bump version to 1.13.1 Bernd Kuhls
2020-08-29 20:56 ` Thomas Petazzoni
2020-08-29 20:40 ` [Buildroot] [PATCH/next 3/3] package/freeswitch: bump version to 1.10.5 Bernd Kuhls
2020-08-29 20:56 ` Thomas Petazzoni
2020-08-29 20:56 ` Thomas Petazzoni [this message]
2020-08-29 22:46 ` [Buildroot] [PATCH/next 1/3] package/spandsp: bump version to 3.0.0 Bernd Kuhls
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=20200829225602.14aa4647@windsurf.home \
--to=thomas.petazzoni@bootlin.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