From: Jon Turney <jon.turney@dronecode.org.uk>
To: Libor Ukropec <ace@seznam.cz>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] python-fasteners 0.16.3
Date: Mon, 18 Apr 2022 14:57:59 +0100 [thread overview]
Message-ID: <8a281c8c-3bac-2734-acde-30258f63286e@dronecode.org.uk> (raw)
In-Reply-To: <f548da19-8848-ff14-4b05-4a69f697cb51@seznam.cz>
On 12/04/2022 20:24, Libor Ukropec wrote:
> Hello, I'd like to maintain the python package python-fasteners
>
> This Python standard library provides a lock for threads (both a
> reentrant one, and a non-reentrant one, see below). Fasteners extends
> this, and provides a lock for processes, as well as Reader Writer locks
> for both threads and processes.
>
>
> This new package is required in order to support more recent version of
> "duplicity" that I adopted.
>
> Please review:
>
> cygport:
> https://github.com/cz6ace/cygwin-python-fasteners
I've added 'python-fasteners' to your authorized packages.
Thanks!
next prev parent reply other threads:[~2022-04-18 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 19:24 Libor Ukropec
2022-04-18 13:57 ` Jon Turney [this message]
2022-04-18 20:49 ` Libor Ukropec
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=8a281c8c-3bac-2734-acde-30258f63286e@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=ace@seznam.cz \
--cc=cygwin-apps@cygwin.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).