All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Lars Kurth <lars.kurth@citrix.com>, Ian Jackson <Ian.Jackson@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Julien Grall <julien.grall@arm.com>,
	Florian Schmidt <Florian.Schmidt@neclab.eu>
Subject: Re: Can someone pls repair patchwork?
Date: Thu, 14 Mar 2019 16:23:32 +0200	[thread overview]
Message-ID: <14940732-0bd7-b502-710d-8519873ccde7@gmail.com> (raw)
In-Reply-To: <06822D85-1C4E-4F1B-8070-D69BD2A4762F@citrix.com>

On 3/6/19 6:02 PM, Lars Kurth wrote:
>
> On 06/03/2019, 16:00, "Ian Jackson" <ian.jackson@citrix.com> wrote:
>
>      Lars Kurth writes ("Re: [Xen-devel] Can someone pls repair patchwork?"):
>      > Hi all, (+ Florian & +Ian, as NEC runs their own patchwork instance and may have some insights)
>      >
>      > before I approach I wanted to ask whether we are sure this has to do with the list change. I am assuming that patchwork gets mails from a registered account on xen-devel. So it is not clear whether the domain change would cause this: see https://patchwork-freedesktop.readthedocs.io/en/latest/installation.html#subscribe-a-local-address-to-the-mailing-list
>      >
>      > Looking at registered e-mails (see png), there appear to be two patchwork instances registered with xen-devel@
>      > * patchwork-xen-devel@patchwork.codeaurora.org
>      > * patchwork-xen-devel@patchwork.kernel.org
>      >
>      > Note that https://patchwork.codeaurora.org/project/xen-devel/list/ seems to have broken at the same time as the kernel.org one
>      >
>      > @Ian: do you know what we did to the lists and/or e-mail handling around that time? Could this be primarily an issue caused by some infrastructure change?
>      
>      I don't remember any dates but we did change the lists from
>      foo@lists.xen.org to foo@lists.xenproject.org for some corporate
>      tradmark branding kind of reason.  I doubt you want to revert that.
>      
>      > Is there a way to check whether mails are actually sent from xen-devel@ to the patchwork instances?
>      > If so, maybe a Credativ ticket is needed
>      
>      I doubt this is the problem.  I think what is needed is for the
>      patchwork instance owners to update their configuration for our new
>      mailing list name.
>      
>      If you look here at this URL Julien provided
>        https://patchwork.kernel.org/project/xen-devel/
>      you see that it says
>        List address  xen-devel@lists.xen.org
>      
>      That is what needs fixing.  Similarly for the codeaurora one I
>      presume.
>      
>      I don't know who "owns" this inside the patchwork.kernel.org system.
>      It says "Maintainers" which is maybe the person who can update the
>      settings, but it is blank.  Maybe the thing is managed by the site
>      administrators then.
>      
>      Unfortunately I could not find contact details for the site admins
>      for either of these anywhere on those websites.
>      
> Oleksandr sent a mail to +webmaster@kernel.org
> Let's see whether anything comes back
>
> If not, I can try and do this via the LF's infrastructure team: they are probably handling this
> Please ping me in a week or so, if that is the case
bump
> Best Regards
> Lars
>
>      
>


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-03-14 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 10:04 Can someone pls repair patchwork? Oleksandr Andrushchenko
2019-03-06 11:17 ` Julien Grall
2019-03-06 12:16   ` Lars Kurth
2019-03-06 16:00     ` Ian Jackson
2019-03-06 16:02       ` Lars Kurth
2019-03-14 14:23         ` Oleksandr Andrushchenko [this message]
2019-03-14 17:05           ` Lars Kurth
2019-03-15  8:46             ` Oleksandr Andrushchenko
2019-03-06 16:02       ` Julien Grall
2019-03-06 12:32   ` Oleksandr Andrushchenko

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=14940732-0bd7-b502-710d-8519873ccde7@gmail.com \
    --to=andr2000@gmail.com \
    --cc=Florian.Schmidt@neclab.eu \
    --cc=Ian.Jackson@citrix.com \
    --cc=julien.grall@arm.com \
    --cc=lars.kurth@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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.