Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 6/7] .gitlab-ci.yml: check flake8
Date: Fri, 30 Mar 2018 23:12:04 +0200	[thread overview]
Message-ID: <20180330211204.GB8894@scaer> (raw)
In-Reply-To: <5aa9ad41d2fec_41fe2ab6b2513450655d5@ultri4.mail>

Ricardo, All,

On 2018-03-14 20:16 -0300, Ricardo Martincoski spake thusly:
> On Tue, Mar 13, 2018 at 03:15 PM, Yann E. MORIN wrote:
> > On 2018-03-13 00:09 -0300, Ricardo Martincoski spake thusly:
> >> ---
> >> BEFORE APPLYING, see this note from Yann:
> >> Note: this can only be applied _after_ we regenerate the docker image.
> >> Then we'll have to update the version of the image at the top of the
> >> gitlab-ci.yml file.
> > Indeed, so I've marked this patch as "deferred" in patchwork, so it does
> > not get accidentally applied.
> Could you regenerate the image, please?
> I don't have the docker push permission.

Not sure if you were aware of it, but this has been done a little while
ago now. Tag 20180318.1724 is available:
    https://hub.docker.com/r/buildroot/base/tags/

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2018-03-30 21:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13  3:09 [Buildroot] [PATCH v3 0/7] fix Python code style v3 Ricardo Martincoski
2018-03-13  3:09 ` [Buildroot] [PATCH v3 1/7] genrandconfig: fix code style Ricardo Martincoski
2018-03-13 21:27   ` Peter Korsgaard
2018-03-13  3:09 ` [Buildroot] [PATCH v3 2/7] size-stats-compare: " Ricardo Martincoski
2018-03-13 21:27   ` Peter Korsgaard
2018-03-13  3:09 ` [Buildroot] [PATCH v3 3/7] test_python_cryptography: " Ricardo Martincoski
2018-03-13  7:39   ` Yegor Yefremov
2018-03-13 21:32   ` Peter Korsgaard
2018-03-13  3:09 ` [Buildroot] [PATCH v3 4/7] scanpypi: " Ricardo Martincoski
2018-03-13  7:39   ` Yegor Yefremov
2018-03-13 21:32   ` Peter Korsgaard
2018-03-13  3:09 ` [Buildroot] [PATCH v3 5/7] support/dockerfile: install flake8 Ricardo Martincoski
2018-03-13 17:22   ` Yann E. MORIN
2018-03-13 21:37   ` Peter Korsgaard
2018-05-27 16:42   ` Yann E. MORIN
2018-05-28  3:00     ` Ricardo Martincoski
2018-05-28 19:44       ` Yann E. MORIN
2018-05-29  3:43         ` Ricardo Martincoski
2018-05-30 15:36           ` Yann E. MORIN
2018-03-13  3:09 ` [Buildroot] [PATCH v3 6/7] .gitlab-ci.yml: check flake8 Ricardo Martincoski
2018-03-13 18:15   ` Yann E. MORIN
2018-03-14 23:16     ` Ricardo Martincoski
2018-03-18 16:25       ` Yann E. MORIN
2018-03-30 21:12       ` Yann E. MORIN [this message]
2018-03-30 22:38         ` Ricardo Martincoski
2018-03-31 20:49   ` Thomas Petazzoni
2018-03-13  3:09 ` [Buildroot] [PATCH v3 7/7] .flake8: ignore utils/diffconfig Ricardo Martincoski
2018-03-13 21:38   ` 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=20180330211204.GB8894@scaer \
    --to=yann.morin.1998@free.fr \
    --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