From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] patchwork.ozlabs.org down, and e-mails not recorded
Date: Mon, 8 Jan 2018 09:10:44 +0100 [thread overview]
Message-ID: <20180108091044.1141f540@windsurf> (raw)
In-Reply-To: <ced2aeb2-82f6-c836-dd5a-e65c6b49c81a@au1.ibm.com>
Hello,
On Mon, 8 Jan 2018 10:33:21 +1100, Andrew Donnellan wrote:
> > Also, since a few weeks, we have seen that patchwork misses some
> > patches that are sent on the Buildroot mailing list. The mails are sent
> > on the mailing list, they are in the mailing list archives, but
> > patchwork does not record them.
> >
> > An example is:
> >
> > http://lists.busybox.net/pipermail/buildroot/2017-December/209885.html
> >
> > PATCH 3/3 was not recorded by patchwork, while other patches in the
> > series have been.
>
> Hmm, looking at the patch list, I also see that patch 2/3 in that series
> (https://patchwork.ozlabs.org/patch/852063/) wasn't correctly identified
> in the same series as patch 1
> (https://patchwork.ozlabs.org/patch/852062/) which is a bit weird.
Note: this issue happened again yesterday. In this series of 4 patches:
http://lists.busybox.net/pipermail/buildroot/2018-January/210935.html
Only patches 2/4 and 4/4 have been recorded by patchwork:
https://patchwork.ozlabs.org/patch/856422/
https://patchwork.ozlabs.org/patch/856423/
Even though all 4 patches have been received through the mailing list.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-08 8:10 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 [this message]
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
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=20180108091044.1141f540@windsurf \
--to=thomas.petazzoni@free-electrons.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