From: Marc Kleine-Budde <mkl@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH v5 0/4] various version bumps
Date: Mon, 17 Oct 2022 14:36:32 +0200 [thread overview]
Message-ID: <20221017123636.54555-1-mkl@pengutronix.de> (raw)
this series contains a few versions bumps.
regards,
Marc
changes since v1: https://lore.ptxdist.org/ptxdist/20220920125705.2728029-1-mkl@pengutronix.de
- clarify subject and patch description for 1/7
changes since v2: https://lore.ptxdist.org/ptxdist/20220920141759.3394460-1-mkl@pengutronix.de
- 1/5 simplify no SSL backend fix (thanks mol)
- 2/5, 3/5, 4/5 update license file checksums
- 5/5 nettle: new patch
- dropped already applied patches
changes since v3: https://lore.ptxdist.org/ptxdist/20220928121609.1209927-1-mkl@pengutronix.de
- 2/5, 3/5, 4/5: explain diff of license files
changes since v4: https://lore.ptxdist.org/ptxdist/20220929145223.1932910-1-mkl@pengutronix.de
- rebase to ptxdist-2022.10.0, after
"[PATCH v4 1/5] libcurl: fix configure if no SSL backend is selected"
has been applied
next reply other threads:[~2022-10-17 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 12:36 Marc Kleine-Budde [this message]
2022-10-17 12:36 ` [ptxdist] [PATCH v5 1/4] bind: version bump to 9.11.37 + adjust license files checksum Marc Kleine-Budde
2022-10-19 5:40 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-10-17 12:36 ` [ptxdist] [PATCH v5 2/4] dhcp: version bump to 4.4.3 " Marc Kleine-Budde
2022-10-19 5:40 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-10-17 12:36 ` [ptxdist] [PATCH v5 3/4] lz4: version bump to 1.9.4 " Marc Kleine-Budde
2022-10-19 5:40 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-10-17 12:36 ` [ptxdist] [PATCH v5 4/4] nettle: version bump to 3.8.1 Marc Kleine-Budde
2022-10-19 5:40 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20221017123636.54555-1-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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