From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: 68649-done@debbugs.gnu.org
Subject: bug#68649: [PATCH 0/3] gnu: Add python-zodb.
Date: Thu, 14 Mar 2024 23:32:04 +0000 [thread overview]
Message-ID: <87ttl8ie4r.fsf@gmail.com> (raw)
In-Reply-To: <87edeaidtd.fsf@troyfigiel.com>
[-- Attachment #1: Type: text/plain, Size: 152 bytes --]
Hi,
I've updated python-zodbpickle to 3.2 build and lint passed successfully
for all 3 patches.
Pushed as fb377b4af7..36da1ad73d to master.
--
Oleg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2024-03-14 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 21:19 [bug#68649] [PATCH 0/3] gnu: Add python-zodb Troy Figiel
2024-01-21 21:12 ` [bug#68649] [PATCH 1/3] gnu: Add python-zconfig Troy Figiel
2024-01-21 21:12 ` [bug#68649] [PATCH 2/3] gnu: Add python-zodbpickle Troy Figiel
2024-01-21 21:13 ` [bug#68649] [PATCH 3/3] gnu: Add python-zodb Troy Figiel
2024-03-14 23:32 ` Sharlatan Hellseher [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ttl8ie4r.fsf@gmail.com \
--to=sharlatanus@gmail.com \
--cc=68649-done@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).