From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [git commit] package/libcgroup: add newline at end of file
Date: Mon, 26 Jun 2023 09:04:05 +0200 [thread overview]
Message-ID: <87edlyogbe.fsf@48ers.dk> (raw)
In-Reply-To: <20230625194428.43A3B851E8@busybox.osuosl.org> (Arnout Vandecappelle via buildroot's message of "Sun, 25 Jun 2023 21:42:57 +0200")
>>>>> "Arnout" == Arnout Vandecappelle via buildroot <buildroot@buildroot.org> writes:
> commit: https://git.buildroot.net/buildroot/commit/?id=fd6b33426962727b97e2ea2a63bfb7a018adcfaf
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> In commit 9d58b525fcfd0d92fcdd3c66d7858213c4b139c6 the newline at the
> end got accidentally removed. Re-add it.
> Reported by check-package.
> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
> ---
> package/libcgroup/Config.in | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
> diff --git a/package/libcgroup/Config.in b/package/libcgroup/Config.in
> index 546b5f3560..9326b967ed 100644
> --- a/package/libcgroup/Config.in
> +++ b/package/libcgroup/Config.in
> @@ -18,4 +18,5 @@ config BR2_PACKAGE_LIBCGROUP_TOOLS
> endif
> comment "libcgroup needs a toolchain w/ C++"
> - depends on !BR2_INSTALL_LIBSTDCPP
> \ No newline at end of file
> + depends on !BR2_INSTALL_LIBSTDCPP
> +
You accidently added 2 newlines, causing checkpackage to complain about
that. Fixed in git now.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-06-26 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 19:42 [Buildroot] [git commit] package/libcgroup: add newline at end of file Arnout Vandecappelle via buildroot
2023-06-26 7:04 ` Peter Korsgaard [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=87edlyogbe.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.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