From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: signatures@kernel.org
Subject: [PATCH 3/3] Release as 0.4.0
Date: Fri, 21 May 2021 14:48:11 -0400 [thread overview]
Message-ID: <20210521184811.617875-3-konstantin@linuxfoundation.org> (raw)
In-Reply-To: <20210521184811.617875-1-konstantin@linuxfoundation.org>
Let's bump to 0.4.0, so we can pull that into b4.
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
---
patatt/__init__.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/patatt/__init__.py b/patatt/__init__.py
index a80f63a..f15ccad 100644
--- a/patatt/__init__.py
+++ b/patatt/__init__.py
@@ -47,7 +47,7 @@ OPT_HDRS = [b'message-id']
KEYCACHE = dict()
# My version
-__VERSION__ = '0.4.0-dev'
+__VERSION__ = '0.4.0'
MAX_SUPPORTED_FORMAT_VERSION = 1
--
2.31.1
prev parent reply other threads:[~2021-05-21 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 18:48 [PATCH 1/3] Sign Message-Id header if present Konstantin Ryabitsev
2021-05-21 18:48 ` [PATCH 2/3] Make header order deterministic Konstantin Ryabitsev
2021-05-21 18:48 ` Konstantin Ryabitsev [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210521184811.617875-3-konstantin@linuxfoundation.org \
--to=konstantin@linuxfoundation.org \
--cc=signatures@kernel.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 NNTP newsgroup(s).