From: Alexander Dahl <ada@thorsis.com>
To: Roland Hieber <rhi@pengutronix.de>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 3/3] rauc: version bump 1.10 -> 1.10.1
Date: Thu, 10 Aug 2023 16:36:59 +0200 [thread overview]
Message-ID: <20230810-nylon-arrive-c0295f694a98@ifak-system.com> (raw)
In-Reply-To: <20230810110256.2242386-3-rhi@pengutronix.de>
Hello Roland,
Am Thu, Aug 10, 2023 at 01:02:56PM +0200 schrieb Roland Hieber:
> Changelog:
> https://github.com/rauc/rauc/releases/tag/v1.10.1
>
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> ---
> .../{rauc-1.10 => rauc-1.10.1}/0001-README-clarify-license.patch | 0
> patches/{rauc-1.10 => rauc-1.10.1}/series | 0
> 2 files changed, 0 insertions(+), 0 deletions(-)
> rename patches/{rauc-1.10 => rauc-1.10.1}/0001-README-clarify-license.patch (100%)
> rename patches/{rauc-1.10 => rauc-1.10.1}/series (100%)
>
> diff --git a/patches/rauc-1.10/0001-README-clarify-license.patch b/patches/rauc-1.10.1/0001-README-clarify-license.patch
> similarity index 100%
> rename from patches/rauc-1.10/0001-README-clarify-license.patch
> rename to patches/rauc-1.10.1/0001-README-clarify-license.patch
> diff --git a/patches/rauc-1.10/series b/patches/rauc-1.10.1/series
> similarity index 100%
> rename from patches/rauc-1.10/series
> rename to patches/rauc-1.10.1/series
Not sure where you got those patches from? They are not in master.
The version bump itself is already in master as commit 196622be0a1b
("rauc: version bump 1.10 -> 1.10.1").
Greets
Alex
next prev parent reply other threads:[~2023-08-10 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 11:02 [ptxdist] [PATCH 1/3] rauc: fix license and add license files checksums Roland Hieber
2023-08-10 11:02 ` [ptxdist] [PATCH 2/3] rauc: select HOST_MESON Roland Hieber
2023-08-10 11:02 ` [ptxdist] [PATCH 3/3] rauc: version bump 1.10 -> 1.10.1 Roland Hieber
2023-08-10 14:36 ` Alexander Dahl [this message]
2023-08-13 19:43 ` Roland Hieber
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=20230810-nylon-arrive-c0295f694a98@ifak-system.com \
--to=ada@thorsis.com \
--cc=ptxdist@pengutronix.de \
--cc=rhi@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