From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Bengt Richter <bokr@bokr.com>
Cc: 40744@debbugs.gnu.org
Subject: bug#40744: guile-2.2.4 (integer-length 0) erroneously returns 0, not 1
Date: Tue, 28 Apr 2020 20:41:10 +0200 [thread overview]
Message-ID: <20200428204110.50e47ad0@alma-ubu> (raw)
In-Reply-To: <20200428200810.7d619d27@alma-ubu>
[-- Attachment #1: Type: text/plain, Size: 323 bytes --]
On Tue, 28 Apr 2020 20:08:10 +0200
Björn Höfling <bjoern.hoefling@bjoernhoefling.de> wrote:
> Bugreport was re-opened under the guile package here:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40855
>
> Closing this one.
Oh, I didn't realize they were merged. So, I reopened them again :-)
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-04-28 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200421130344.GA9369@LionPure>
[not found] ` <20200425213350.GA10462@LionPure>
2020-04-28 18:08 ` bug#40744: guile-2.2.4 (integer-length 0) erroneously returns 0, not 1 Björn Höfling
2020-04-28 18:41 ` Björn Höfling [this message]
2021-07-16 3:01 ` Rob Browning
2021-07-24 17:12 ` Bengt Richter
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200428204110.50e47ad0@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=40744@debbugs.gnu.org \
--cc=bokr@bokr.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).