Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [2018.02.x 2/2] support/testing: add test for file capabilities
Date: Fri, 10 Aug 2018 08:32:28 +0200	[thread overview]
Message-ID: <87va8ienpf.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180806031715.7088-2-ricardo.martincoski@gmail.com> (Ricardo Martincoski's message of "Mon, 6 Aug 2018 00:17:15 -0300")

>>>>> "Ricardo" == Ricardo Martincoski <ricardo.martincoski@gmail.com> writes:

 > Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com>
 > ---
 > complete run on GitLab CI on top of 2018.02.4 with the series applied:
 > https://gitlab.com/RicardoMartincoski/buildroot/pipelines/27226377

 > only the test on top of 2018.02.4:
 > https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/86985431

 > only the test on top of 2018.05.1:
 > https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/86985455

 > only the test on top of 2018.08-rc1:
 > https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/86985484

I know it fails on master, but then we are atleast aware of it, so:

Committed to master, and then backported to 2018.02.x and 2018.05.x, thanks.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2018-08-10  6:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-06  3:17 [Buildroot] [2018.02.x 1/2] makedevs: allow leading whitespace for capabilities Ricardo Martincoski
2018-08-06  3:17 ` [Buildroot] [2018.02.x 2/2] support/testing: add test for file capabilities Ricardo Martincoski
2018-08-10  2:21   ` Ricardo Martincoski
2018-08-10  6:32   ` Peter Korsgaard [this message]
2018-08-09 21:42 ` [Buildroot] [2018.02.x 1/2] makedevs: allow leading whitespace for capabilities Thomas Petazzoni
2018-08-10  2:18   ` Ricardo Martincoski
2018-08-10  6:29     ` Peter Korsgaard
2018-08-10  6:28   ` Peter Korsgaard

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=87va8ienpf.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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