Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] support/dependencies/dependencies.sh: awk is needed by Buildroot
Date: Thu, 8 May 2025 20:02:53 +0200	[thread overview]
Message-ID: <20250508200253.183a9660@windsurf> (raw)
In-Reply-To: <8734dfzqc2.fsf@tarshish>

Hello Baruch,

On Thu, 08 May 2025 07:19:57 +0300
Baruch Siach <baruch@tkos.co.il> wrote:

> [...]
> > diff --git a/docs/manual/prerequisite.adoc b/docs/manual/prerequisite.adoc
> > index 5d3aa297a9..9ccc30cca0 100644
> > --- a/docs/manual/prerequisite.adoc
> > +++ b/docs/manual/prerequisite.adoc
> > @@ -38,6 +38,7 @@ between distributions).
> >  ** +file+ (must be in +/usr/bin/file+)
> >  ** +bc+
> >  ** +findutils+
> > +**  awk  
> 
> Any reason to make text formatting for this item different than all
> other listed packages?

Obviously no reason, but here is my excuse: my Emacs apparently has
some AsciiDoc mode, so instead of showing +findutils+, it was showing
findutils without + signs around, but in a blue color. So I didn't
really realize I should use +awk+. Yes, I should have reviewed the diff :-)

Thanks a lot for spotting, I have sent a v2.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2025-05-08 18:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 20:11 [Buildroot] [PATCH] support/dependencies/dependencies.sh: awk is needed by Buildroot Thomas Petazzoni via buildroot
2025-05-08  4:19 ` Baruch Siach via buildroot
2025-05-08 18:02   ` Thomas Petazzoni via buildroot [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=20250508200253.183a9660@windsurf \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=thomas.petazzoni@bootlin.com \
    /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