Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13296] host-libcap failed to build
Date: Sun, 15 Nov 2020 15:48:00 +0000	[thread overview]
Message-ID: <bug-13296-163-9fQPnlmRfJ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13296-163@https.bugs.busybox.net/>

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

Heiko Thiery <heiko.thiery@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #16 from Heiko Thiery <heiko.thiery@gmail.com> ---
fixed with 7540fbe877d48d75113338430ce3304a00a82cb1

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

      parent reply	other threads:[~2020-11-15 15:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05  9:10 [Buildroot] [Bug 13296] New: host-libcap failed to build bugzilla at busybox.net
2020-11-05 12:10 ` [Buildroot] [Bug 13296] " bugzilla at busybox.net
2020-11-05 16:22 ` bugzilla at busybox.net
2020-11-05 16:22 ` bugzilla at busybox.net
2020-11-05 16:35 ` bugzilla at busybox.net
2020-11-05 19:03 ` bugzilla at busybox.net
2020-11-05 19:05 ` bugzilla at busybox.net
2020-11-05 19:06 ` bugzilla at busybox.net
2020-11-06  7:28 ` bugzilla at busybox.net
2020-11-06  7:31 ` bugzilla at busybox.net
2020-11-06  7:38 ` bugzilla at busybox.net
2020-11-09 22:13 ` bugzilla at busybox.net
2020-11-10  9:33 ` bugzilla at busybox.net
2020-11-10 11:21 ` bugzilla at busybox.net
2020-11-10 15:01 ` bugzilla at busybox.net
2020-11-11 12:00 ` bugzilla at busybox.net
2020-11-11 12:05 ` bugzilla at busybox.net
2020-11-15 15:48 ` bugzilla at busybox.net [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=bug-13296-163-9fQPnlmRfJ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox