From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/bc: bump to 1.07.1
Date: Fri, 13 Sep 2019 20:31:45 +0200 [thread overview]
Message-ID: <20190913203145.2e05eb85@windsurf.home> (raw)
In-Reply-To: <CANQCQpY_HqqxoUkAOcxN0_ORRnYLTdUdfBXC=5ZfShXOWCDeCg@mail.gmail.com>
Hello Matt,
On Fri, 13 Sep 2019 13:14:10 -0500
Matthew Weber <matthew.weber@collins.com> wrote:
> For the patches that were kept in this bump, they were all still
> pending and on the debian / yocto distro patch lists. I wasn't able
> to find any upstream submissions. Are patches against gnu tools like
> bc done directly to the maintainer ( Phil Nelson
> <philnelson@acm.org>)? I could definitely send them out to him if
> that makes sense.
Yes, I already contributed a patch to bc a while ago, and indeed, I
sent it directly to the upstream author. Interestingly, the patch and
discussion I had were precisely about libmath being re-generated, and
that was last year.
He had sent me some test versions of bc 1.07.2 which should have fixed
the problem, but I never took the time to reply it seems :-/
These projects with no mailing list, bug tracker or public version
control system are really difficult to work with :-/
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-13 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 20:50 [Buildroot] [PATCH] package/bc: bump to 1.07.1 Matt Weber
2019-09-13 17:46 ` Thomas Petazzoni
2019-09-13 18:14 ` Matthew Weber
2019-09-13 18:31 ` Thomas Petazzoni [this message]
2019-09-13 18:34 ` Thomas Petazzoni
2019-09-13 18:40 ` [Buildroot] [External] " Matthew Weber
2019-09-13 19:53 ` Thomas Petazzoni
2019-09-13 18:34 ` [Buildroot] " Matthew Weber
2019-09-13 18:37 ` Thomas Petazzoni
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=20190913203145.2e05eb85@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