From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Cc: Julien Olivain <ju.o@free.fr>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/tcl: fix package patch
Date: Mon, 25 Sep 2023 15:57:14 +0200 [thread overview]
Message-ID: <87zg1abbk5.fsf@48ers.dk> (raw)
In-Reply-To: <337d9023-7587-ef8f-3e61-f7bd16f333ff@mind.be> (Arnout Vandecappelle via buildroot's message of "Thu, 21 Sep 2023 20:51:40 +0200")
>>>>> "Arnout" == Arnout Vandecappelle via buildroot <buildroot@buildroot.org> writes:
> On 18/09/2023 21:45, Julien Olivain wrote:
>> The commit 4e365d1768 "package/tcl: bump to version 8.6.13" did NOT
>> refreshed the package patch, because the patch was still applying
>> correctly and the package was working as expected.
>> It was refreshed in the previous bump, in commit 9cf314745a
>> "package/tcl: bump to version 8.6.12".
> I've added here that this commit was part of 2022.02, to make it
> easier for Peter to know that it should be backported.
> It was my original mistake to commit that incorrect change, so I've
> committed the fix as well :-)
> Applied to master, thanks.
So this presumably means it needs to be backported even though it
apparently worked (or built at least) without / with the dummy patch?
Committed to 2023.02.x, 2023.05.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-25 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 19:45 [Buildroot] [PATCH 1/1] package/tcl: fix package patch Julien Olivain
2023-09-21 18:51 ` Arnout Vandecappelle via buildroot
2023-09-25 13:57 ` Peter Korsgaard [this message]
2023-09-25 14:21 ` Arnout Vandecappelle via buildroot
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=87zg1abbk5.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=ju.o@free.fr \
/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