From: Julien Grall <julien.grall@arm.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>,
xen-devel <xen-devel@lists.xenproject.org>,
"lars.kurth@citrix.com" <lars.kurth@citrix.com>
Subject: Re: Can someone pls repair patchwork?
Date: Wed, 6 Mar 2019 11:17:16 +0000 [thread overview]
Message-ID: <f6f98db5-ee05-2c11-1b57-dd7c80e7b56f@arm.com> (raw)
In-Reply-To: <332e7348-d711-2d02-02e0-3d264f2955f6@gmail.com>
(+ Lars)
On 06/03/2019 10:04, Oleksandr Andrushchenko wrote:
> To whom it may concern
Hi Oleksandr,
>
> Since late 2017 the very useful Patchwork resource [1]
> stopped working after (as I assume) Xen-devel list has changed
> its address from xen-devel@lists.xen.org to the current one.
> Patchwork is still configured to the old one, so recent
> patches are not archived.
> Could the respective owner from Xen community please take a look at [2]
> and make Patchwork work again? In particular Patchwork is
> very useful when you need a patch in mbox format without pain.
Patchwork is hosted by the kernel community. So it would be best if you contact
them directly. [3].
Cheers,
> [1] https://patchwork.kernel.org/project/xen-devel/list/
> [2] https://patchwork.kernel.org/project/xen-devel/
[3] https://www.kernel.org/category/contact-us.html
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-03-06 11:17 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 [this message]
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
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=f6f98db5-ee05-2c11-1b57-dd7c80e7b56f@arm.com \
--to=julien.grall@arm.com \
--cc=andr2000@gmail.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.