From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] patchwork.ozlabs.org down, and e-mails not recorded
Date: Sun, 8 Jul 2018 11:34:55 +0200 [thread overview]
Message-ID: <20180708093455.GB2474@scaer> (raw)
In-Reply-To: <c5bfa3f1-3d33-bfac-5cf3-3de3204bb878@ozlabs.org>
Jeremy, All,
On 2018-03-20 20:19 +0800, Jeremy Kerr spake thusly:
[--SNIP--]
> Let me know how things go over the next few days.
So it's been more than a few days, but I recently caught another issue
about series for the buildroot mailing list.
The following three patches should be grouped together, but only 1 and 3
are:
https://patchwork.ozlabs.org/project/buildroot/list/?series=54291
https://patchwork.ozlabs.org/patch/940910/ [1/3]
https://patchwork.ozlabs.org/patch/940911/ [2/3]
https://patchwork.ozlabs.org/patch/940912/ [3/3]
And of those 5 patches, patch 2 is also missing:
https://patchwork.ozlabs.org/project/buildroot/list/?series=54286
https://patchwork.ozlabs.org/patch/940895/ [1/5]
https://patchwork.ozlabs.org/patch/940894/ [2/5]
https://patchwork.ozlabs.org/patch/940897/ [3/5]
https://patchwork.ozlabs.org/patch/940896/ [4/5]
https://patchwork.ozlabs.org/patch/940898/ [5/5]
And another 3-patch series, with patch 3 failign to get grouped:
https://patchwork.ozlabs.org/project/buildroot/list/?series=54129
https://patchwork.ozlabs.org/patch/940542/ [1/3]
https://patchwork.ozlabs.org/patch/940540/ [2/3]
https://patchwork.ozlabs.org/patch/940539/ [3/3]
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-07-08 9:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 20:43 [Buildroot] patchwork.ozlabs.org down, and e-mails not recorded Thomas Petazzoni
2018-01-07 23:33 ` Andrew Donnellan
2018-01-08 8:10 ` Thomas Petazzoni
2018-02-05 21:45 ` Thomas Petazzoni
2018-02-06 8:41 ` Andrew Donnellan
2018-02-06 9:03 ` Jeremy Kerr
2018-02-06 9:55 ` Thomas Petazzoni
2018-02-13 22:19 ` Thomas Petazzoni
2018-02-14 3:56 ` Andrew Donnellan
2018-02-14 8:01 ` Thomas Petazzoni
[not found] ` <87lgftau6p.fsf@linkitivity.dja.id.au>
2018-02-16 14:49 ` Thomas Petazzoni
2018-02-17 3:29 ` Andrew Donnellan
2018-03-10 11:58 ` Peter Korsgaard
[not found] ` <20180312015055.3dc9789c@canb.auug.org.au>
2018-03-12 4:57 ` Jeremy Kerr
2018-03-20 12:19 ` Jeremy Kerr
2018-03-20 15:08 ` Thomas Petazzoni
2018-03-31 16:27 ` Yann E. MORIN
2018-03-31 16:29 ` Yann E. MORIN
2018-07-08 9:34 ` Yann E. MORIN [this message]
2018-03-12 19:53 ` daggs
2018-03-12 21:23 ` 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=20180708093455.GB2474@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.