Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN via buildroot" <buildroot@buildroot.org>
To: "José Luis Salvador Rufo" <salvador.joseluis@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Compilation Issue with Commit 793ebd5d28095c8df45a0d183d273d8a84b3f0a4
Date: Sat, 29 Nov 2025 18:53:55 +0100	[thread overview]
Message-ID: <aSszM90msDWGlEaa@landeda> (raw)
In-Reply-To: <CAH+XeQYPBnXkXq4Fu0aBJ2UBR_U31ypza4z-1jf2Y78aWWiv-g@mail.gmail.com>

José, All,

On 2025-11-29 18:14 +0100, José Luis Salvador Rufo spake thusly:
> The commit 793ebd5d28095c8df45a0d183d273d8a84b3f0a4 broke my compilation.

Please explain what the problem is.

> An AI suggested that the problem is because the script
> `support/scripts/check-merged` requires the following change:

Did you understand why the suggested change is correct?

In the end, I don't think we specifically care how you came up with the
proposed change, but we need to know why this is correct. We don't need
some hand-waving "I don't understand why but it works, magic!", but
rather an explanation for why this is needed. This is needed for the
future, when we eventually need to revisit that commit later on, to
understand why we thought the fix was correct back then, and see if some
assumptions valid right now would still be then.

However, thanks for disclosing the use of an AI agent; note that my
reply would have been the same even if you had not.

Would you care to resubmit this patch with a proper commit log (look at
the history to get some ideas); you can also look at some directions in
the manual (it is a bit verbose, but contains a lot of important
information):

    https://buildroot.org/downloads/manual/manual.html#submitting-patches

Also, please add in the commit log that this fixes a [previous commit,
e.g. with a line readoing;

    Fixes: 793ebd5d28095c8df45a0d183d273d8a84b3f0a4

When you do that, you can add my:

    Reviewed-by: Yann E. MORIN <yann.morin.1998@free.fr>

Regards,
Yann E. MORIN.

> diff --git a/support/scripts/check-merged b/support/scripts/check-merged
> index 447abfd815..23fdaac2c8 100755
> --- a/support/scripts/check-merged
> +++ b/support/scripts/check-merged
> @@ -47,6 +47,8 @@ while getopts "t:ub" OPT; do
>         esac
>  done
> 
> +shift $((OPTIND-1))
> +
>  if [ "${type}" = "skeleton" ]; then
>         strict=true
>  else
> 
> After applying this change, my compilation works again, in the same
> way as reverting commit 793ebd5d28095c8df45a0d183d273d8a84b3f0a4.
> I haven’t checked the reason for this `shift` myself.
> 
> Greetings.

-- 
.-----------------.--------------------.------------------.--------------------.
|  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

  reply	other threads:[~2025-11-29 17:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-29 17:14 [Buildroot] Compilation Issue with Commit 793ebd5d28095c8df45a0d183d273d8a84b3f0a4 José Luis Salvador Rufo
2025-11-29 17:53 ` Yann E. MORIN via buildroot [this message]
2025-11-29 19:35   ` Edgar Bonet via buildroot
2025-11-29 20:23     ` Yann E. MORIN via buildroot
2025-11-29 20:38     ` José Luis Salvador Rufo
2025-11-29 21:46       ` José Luis Salvador Rufo
2025-11-30  7:36         ` Yann E. MORIN 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=aSszM90msDWGlEaa@landeda \
    --to=buildroot@buildroot.org \
    --cc=salvador.joseluis@gmail.com \
    --cc=yann.morin.1998@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