From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] patchwork.ozlabs.org down, and e-mails not recorded
Date: Mon, 5 Feb 2018 22:45:00 +0100 [thread overview]
Message-ID: <20180205224500.1a34e02a@windsurf> (raw)
In-Reply-To: <20180108091044.1141f540@windsurf>
Hello,
On Mon, 8 Jan 2018 09:10:44 +0100, Thomas Petazzoni wrote:
> > 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/
This is still happening, and pretty badly. Sometimes almost entire
series are skipped. Most recent example is this series:
http://lists.busybox.net/pipermail/buildroot/2018-February/213111.html
It has 15 patches and a cover letter, and all what patchwork recorded
is:
https://patchwork.ozlabs.org/patch/869198/
https://patchwork.ozlabs.org/patch/869197/
Only two patches out of 15 + a cover letter. Not great.
Is there anything that can be done about this ? An example of
Message-Id that was not recorded is:
Message-Id: <8027bae45d8e041c8a1e0bc714ab378ff984ded3.1517820133.git.yann.morin.1998@free.fr>
Thanks a lot,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-05 21:45 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 [this message]
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=20180205224500.1a34e02a@windsurf \
--to=thomas.petazzoni@bootlin.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 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.