From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "J. Neuschäfer" <j.neuschaefer@gmx.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] {skalibs, execline, mdevd, s6, s6-{rc, linux-init, {linux, portable}-utils, networking}}: bump
Date: Fri, 31 May 2024 11:35:50 +0200 [thread overview]
Message-ID: <ZlmZ9uQdSgv36LaK@landeda> (raw)
In-Reply-To: <20240530-s6-update-v1-1-8088e16a1cf4@gmx.net>
J., All,
Thanks for this patch.
On 2024-05-30 22:32 +0200, J. Neuschäfer via buildroot spake thusly:
> Update all skarnet.org packages to their current upstream version.
>
> diff COPYING (slightly different between packages):
> -Copyright (c) 2011-2022 Laurent Bercot <ska-skaware@skarnet.org>
> +Copyright (c) 2011-2024 Laurent Bercot <ska-skaware@skarnet.org>
In a commit log, we want human-readable explanaltions, not a
(pseudo-)diff; so just state something like:
Update hashes of license files for an update in copyright years.
> Signed-off-by: J. Neuschäfer <j.neuschaefer@gmx.net>
> ---
> This patch(set) updates the packages from skarnet.org. It is one commit
> to avoid build failures due to incompatible versions:
Thanks for the explanations. It should be in the commit log, so that
when we eefer to that commit in the future, we immediately understand
why they were all bumped together.
> For example, when
> I only update skalibs to 2.14.1.1 and leave the rest as is, execline
> fails to build.
Is it possible to do the reverse: bump skalibs last? I.e. would the
newer execline (and other packages) still build and run OK with the
current skalibs version, or are they really so tightly coupled?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-31 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 20:32 [Buildroot] [PATCH] {skalibs, execline, mdevd, s6, s6-{rc, linux-init, {linux, portable}-utils, networking}}: bump J. Neuschäfer via buildroot
2024-05-31 9:35 ` Yann E. MORIN [this message]
2024-06-01 8:50 ` J. Neuschäfer via buildroot
2024-06-01 9:13 ` Yann E. MORIN
2024-06-01 11:15 ` J. Neuschäfer via buildroot
2024-06-01 9:51 ` Yann E. MORIN
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=ZlmZ9uQdSgv36LaK@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=j.neuschaefer@gmx.net \
/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