All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13216] [Documentation] 2020.02.6 requires GNU find utils
Date: Tue, 29 Sep 2020 18:49:53 +0000	[thread overview]
Message-ID: <bug-13216-163-yRsgNzQITx@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13216-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=13216

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #2 from Peter Korsgaard <jacmet@uclibc.org> ---
Thanks for the report, I have added the 2020.02.6 release now, I must have
missed adding it when I made the release.

The -print0 option is used in quite a lot of places (and may be used by the
build system of various packages as well), so I guess the only sensible
solution is to update our documentation.

Out of interest, what find implementation are you using? Even the busybox
applet supports it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-09-29 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22  2:42 [Buildroot] [Bug 13216] New: [Documentation] 2020.02.6 requires GNU find utils bugzilla at busybox.net
2020-09-22  2:43 ` [Buildroot] [Bug 13216] " bugzilla at busybox.net
2020-09-29 18:46 ` bugzilla at busybox.net
2020-09-29 18:49 ` bugzilla at busybox.net [this message]
2020-09-29 19:47 ` bugzilla at busybox.net
2020-09-29 22:40 ` bugzilla at busybox.net
2022-09-18 12:58 ` bugzilla

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=bug-13216-163-yRsgNzQITx@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.