From: "thierry.reding@gmail.com via RT" <kernel-helpdesk@rt.linuxfoundation.org>
To: u.kleine-koenig@pengutronix.de
Cc: linux-pwm@vger.kernel.org
Subject: Re: [Kernel.org Helpdesk #89942] Re: adding linux-pwm archives to lore.kernel.org?
Date: Mon, 27 Jul 2020 07:20:26 +0000 [thread overview]
Message-ID: <010101738f24e579-b69d3897-b823-41f6-994c-2755312a9af9-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <20200727072021.GA2780715@ulmo>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
On Thu, Jul 23, 2020 at 05:38:45PM +0000, Konstantin Ryabitsev via RT wrote:
> On Thu, Jul 23, 2020 at 05:27:04PM +0000, Uwe Kleine-König via RT wrote:
> > > I'm sorry, apparently I screwed up and didn't assign this ticket to
> > > anyone when it came in. I was dutifully ignoring follow-ups, as I'd
> > > assumed someone else would be responding.
> > >
> > > Chris, I've properly assigned it to you now -- can you please
> > > prioritise this request, as time allows?
> >
> > Last week I thought this is a no-brainer now and will be done in a few
> > hours. It seems I was wrong :-|
>
> I do appreciate your patience. There is a lot of other work happening at
> the IT team, so your request for adding a mailing list archive has to
> contend for staff resources with many other ongoing projects.
We've made do without the archive up to now, so I think we can wait a
bit longer. I think Uwe might just be worried that this fell through the
cracks again. If it didn't, I'm sure we can be patient for a bit longer.
Thierry
[-- Attachment #2: Type: application/x-rt-original-message, Size: 5990 bytes --]
next prev parent reply other threads:[~2020-07-27 7:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-89942@linuxfoundation>
2020-02-13 10:26 ` adding linux-pwm archives to lore.kernel.org? Uwe Kleine-König
2020-05-23 17:05 ` Uwe Kleine-König
2020-05-25 8:54 ` Thierry Reding
2020-05-25 8:54 ` [Kernel.org Helpdesk #89942] [linuxfoundation.org #89942] " thierry.reding@gmail.com via RT
2020-06-13 14:15 ` Uwe Kleine-König
2020-06-13 14:15 ` [Kernel.org Helpdesk #89942] [linuxfoundation.org #89942] " Uwe Kleine-König via RT
2020-07-09 9:26 ` Uwe Kleine-König
2020-07-09 9:27 ` [Kernel.org Helpdesk #89942] [linuxfoundation.org #89942] " Uwe Kleine-König via RT
[not found] ` <rt-4.4.0-1686-1594286826-1167.89942-6-0@linuxfoundation>
2020-07-14 21:27 ` [Kernel.org Helpdesk " Konstantin Ryabitsev via RT
2020-07-23 17:27 ` Uwe Kleine-König
2020-07-23 17:27 ` Uwe Kleine-König via RT
[not found] ` <010101737cb6d988-bb70d517-bbf8-44b0-aa3d-4f9eed9101f3-000000@us-west-2.amazonses.com>
[not found] ` <20200723173841.4geg4blngc2fwp4z@chatter.i7.local>
2020-07-23 17:38 ` Konstantin Ryabitsev via RT
2020-07-27 7:20 ` Thierry Reding
2020-07-27 7:20 ` thierry.reding@gmail.com via RT [this message]
[not found] ` <0101017398e048cb-4976944a-cc5c-4183-a073-1bf01692ec77-000000@us-west-2.amazonses.com>
[not found] ` <20200729072459.c6gwkr224lcbmd7r@pengutronix.de>
2020-07-29 7:25 ` Uwe Kleine-König via RT
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=010101738f24e579-b69d3897-b823-41f6-994c-2755312a9af9-000000@us-west-2.amazonses.com \
--to=kernel-helpdesk@rt.linuxfoundation.org \
--cc=linux-pwm@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).