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] patchwork.ozlabs.org down, and e-mails not recorded
Date: Sat, 31 Mar 2018 18:27:45 +0200	[thread overview]
Message-ID: <20180331162745.GM25161@scaer> (raw)
In-Reply-To: <20180320160847.2ef26965@windsurf>

Hello guys!

On 2018-03-20 16:08 +0100, Thomas Petazzoni spake thusly:
> On Tue, 20 Mar 2018 20:19:01 +0800, Jeremy Kerr wrote:
> > Good news: with the logging we had in place recently (and a fix to
> > correct error reporting), it looks like we've found the problem with
> > parsing emails from a series. This issue was recently addressed by
> > Daniel, so I've updated patchwork.ozlabs.org to run the current
> > stable/2.0 branch, which has fixes for these. Hopefully this resolves
> > the issue with dropped patches.
> > 
> > The update should also make the mail parser a little more robust against
> > transient failures too.
> > 
> > Let me know how things go over the next few days.
> 
> Thanks a lot for this debugging effort! We'll monitor how patchwork
> behaves in the next days and give you some feedback (good or bad).

Thanks indeed! :-)

We've got a little follow up issue now: some patches are not attributed
to the series they belong too, for example:
    https://patchwork.ozlabs.org/patch/893732/

should belong to:
    https://patchwork.ozlabs.org/project/buildroot/list/?series=36782

Similarly:
    https://patchwork.ozlabs.org/patch/893678/

should belong to:
    https://patchwork.ozlabs.org/project/buildroot/list/?series=36757

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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-03-31 16:27 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 [this message]
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=20180331162745.GM25161@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