From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] More maintainers
Date: Sat, 5 Sep 2020 22:54:28 +0200 [thread overview]
Message-ID: <20200905205428.GB14354@scaer> (raw)
In-Reply-To: <20200905202557.GZ14354@scaer>
Adam, All,
On 2020-09-05 22:25 +0200, Yann E. MORIN spake thusly:
> On 2020-09-05 09:20 -0700, Adam Duskett spake thusly:
> > Here's a simple test:
> > https://patchwork.ozlabs.org/project/buildroot/patch/20191112162325.529637-2-m.niestroj at grinn-global.com/
So, I have now had a look at that pending patch.
I tried to apply it to master, but it failed: there is a conflict.
And indeed, we've had that test since 2020-03-24, with commit 803fc6ad51
(support/testing: add netdata test).
The patch still pending is v3 of the patchset, while there has been a
v4, a v5, and eventually a v6, which was applied.
Thus the pending patch is just some missed-to-be-updated patch in
patchwork; I've now marked it as superseded.
Thanks, I like it when the backlog decreases. ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-09-05 20:54 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 17:34 [Buildroot] More maintainers Adam Duskett
2020-08-27 19:35 ` Angelo Compagnucci
2020-08-27 20:39 ` Thomas Petazzoni
2020-08-29 9:50 ` Yann E. MORIN
2020-09-02 17:53 ` Adam Duskett
2020-09-02 20:08 ` Arnout Vandecappelle
2020-09-02 20:11 ` Adam Duskett
2020-09-02 21:51 ` Christian Stewart
2020-09-03 15:44 ` Avraham Shukron
2020-09-03 16:24 ` Thomas Petazzoni
2020-09-03 16:44 ` Angelo Compagnucci
2020-09-03 17:29 ` Adam Duskett
2020-09-04 8:31 ` Nicolas Cavallari
2020-09-04 17:39 ` Peter Korsgaard
2020-09-04 18:12 ` Michael Nazzareno Trimarchi
2020-09-04 19:05 ` Peter Korsgaard
2020-09-04 19:36 ` Angelo Compagnucci
2020-09-04 21:10 ` Peter Korsgaard
2020-09-05 4:52 ` Christian Stewart
2020-09-05 6:44 ` Peter Korsgaard
2020-09-05 16:20 ` Adam Duskett
2020-09-05 17:25 ` Peter Korsgaard
2020-09-05 19:16 ` Thomas Petazzoni
2020-09-05 20:10 ` Angelo Compagnucci
2020-09-05 20:38 ` Thomas Petazzoni
2020-09-05 20:55 ` Angelo Compagnucci
2020-09-05 21:04 ` Thomas Petazzoni
2020-09-05 21:34 ` Angelo Compagnucci
2020-09-05 22:25 ` Adam Duskett
2020-09-06 7:43 ` Peter Korsgaard
2020-09-06 7:58 ` Yegor Yefremov
2020-09-07 15:02 ` Heiko Thiery
2020-09-07 15:20 ` Thomas Petazzoni
2020-09-07 15:43 ` Heiko Thiery
2020-09-10 22:30 ` Christian Stewart
2020-09-05 20:25 ` Yann E. MORIN
2020-09-05 20:54 ` Yann E. MORIN [this message]
2020-09-05 18:59 ` Alexander Dahl
2020-09-05 19:17 ` Peter Korsgaard
2020-09-05 20:06 ` Christian Stewart
2020-09-04 17:30 ` James Hilliard
2020-09-03 16:28 ` Angelo Compagnucci
2020-09-04 18:52 ` Peter Korsgaard
2020-09-03 18:39 ` Christian Stewart
2020-09-07 15:57 ` Michael Nosthoff
2020-09-07 18:35 ` Alexander Dahl
2020-09-09 6:14 ` Peter Korsgaard
2020-09-05 13:06 ` [Buildroot] More maintainers: a live discussion ? Thomas Petazzoni
2020-09-07 8:02 ` Thomas Petazzoni
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=20200905205428.GB14354@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 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.