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 11216] Capabilities not applied to filesystem
Date: Mon, 12 Nov 2018 17:39:32 +0000	[thread overview]
Message-ID: <bug-11216-163-dWoPP3qXVI@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11216-163@https.bugs.busybox.net/>

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

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Extended attributes not     |Capabilities not applied to
                   |applied to filesystem       |filesystem

--- Comment #3 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Ricardo, All,

Also, I've edited the title of this BZ, because it really relates
to capabilities. Our makedevs syntax only allows for specifying
capabilities, not arbitrary extended attributes.

Regards,
Yann E. MORIN.

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

  parent reply	other threads:[~2018-11-12 17:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10  2:08 [Buildroot] [Bug 11216] New: Extended attributes not applied to filesystem bugzilla at busybox.net
2018-10-14 16:42 ` [Buildroot] [Bug 11216] " bugzilla at busybox.net
2018-11-02 10:58 ` bugzilla at busybox.net
2018-11-12 17:37 ` bugzilla at busybox.net
2018-11-12 17:39 ` bugzilla at busybox.net [this message]
2018-11-13  7:18 ` [Buildroot] [Bug 11216] Capabilities " bugzilla at busybox.net

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-11216-163-dWoPP3qXVI@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