From: Rob Browning <rlb@defaultvalue.org>
To: guile-devel@gnu.org
Subject: Re: [PATCH 0/8] Move py C utility code to pyutil; guard overflow
Date: Tue, 30 May 2023 20:54:05 -0500 [thread overview]
Message-ID: <87sfbdjmf6.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <20230531004944.1657633-1-rlb@defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> Proposed for main.
>
> This starts moving some of the utility functions to src/bup/pyutil.*,
> so that we can use them everywhere, e.g. hashsplit, bupsplit...
Apologies. Clearly the wrong git send-email address.
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
prev parent reply other threads:[~2023-05-31 1:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 0:49 [PATCH 0/8] Move py C utility code to pyutil; guard overflow Rob Browning
2023-05-31 0:49 ` [PATCH 1/8] bup_shared_cflags: add -Winline Rob Browning
2023-05-31 0:49 ` [PATCH 2/8] Create src/pyutil.c for utility functions Rob Browning
2023-05-31 0:49 ` [PATCH 3/8] pyutil: add INTEGER_TO_PY as BUP_LONGISH_TO_PY Rob Browning
2023-05-31 0:49 ` [PATCH 4/8] pyutil: add bup_uint_from_py bup_ulong_from_py bup_ullong_from_py Rob Browning
2023-05-31 0:49 ` [PATCH 5/8] pyutil: add BUP_ASSIGN_PYLONG_TO_INTEGRAL; use EXPR_SIGNED Rob Browning
2023-05-31 0:49 ` [PATCH 6/8] _helpers: remove vestigial py2 utimes related code Rob Browning
2023-05-31 0:49 ` [PATCH 7/8] HashSplitter_init: guard against bits/fanbits overflow Rob Browning
2023-05-31 0:49 ` [PATCH 8/8] Reject bup_getpwuid bup_getgrgid argument overflow Rob Browning
2023-05-31 1:54 ` Rob Browning [this message]
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=87sfbdjmf6.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
/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).