From: Daniel Axtens <dja@axtens.net>
To: Han-Wen Nienhuys <hanwen@google.com>, workflows@vger.kernel.org
Subject: Re: Lyon meeting notes
Date: Wed, 30 Oct 2019 09:35:08 +1100 [thread overview]
Message-ID: <87wocnmb8j.fsf@dja-thinkpad.axtens.net> (raw)
In-Reply-To: <CAFQ2z_PiNzDeBT7mnprRdk2kf==HoBU1HM7NT4hgFns1wt4WVg@mail.gmail.com>
Hi all,
> I tried to take some notes at the session today. They're a bit rough,
> but I hope they'll be useful to someone.
>
> https://docs.google.com/document/d/1khLOBw5-HyaaNX7xregpHQLSfvGDUeHDY921bkI-_os/edit?usp=sharing
I can't quite make sense of the notes for Patchwork, but if you have
specific asks for us, we can try to target them for Patchwork 3.0, which
I expect will come out some time next year. (Modulo most of us doing
this as a hobby, of course.)
> KR: write local command to work with patchwork.
We have a couple of local commands already, pwclient and git-pw. Is
there something new that would be helpful?
As an aside, I know offline stuff has come up a few times, and I think
it should be reasonably straightforward to make a caching API client
that can buffer your requests until you're next online. I don't have any
cycles to do this, but I'm happy to help anyone who does.
Regards,
Daniel
next prev parent reply other threads:[~2019-10-29 22:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 15:41 Han-Wen Nienhuys
2019-10-29 22:26 ` Eric Wong
2019-10-29 23:13 ` Bjorn Helgaas
2019-11-01 20:07 ` Konstantin Ryabitsev
2019-11-01 20:46 ` Geert Uytterhoeven
2019-11-01 21:30 ` Theodore Y. Ts'o
2019-11-02 1:17 ` Eric Wong
2019-11-01 21:34 ` Dmitry Vyukov
2019-10-29 22:35 ` Daniel Axtens [this message]
2019-11-01 17:29 ` Konstantin Ryabitsev
2019-11-01 17:35 ` Dmitry Vyukov
2019-11-02 11:46 ` Steven Rostedt
2019-10-30 9:21 ` Jonathan Corbet
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=87wocnmb8j.fsf@dja-thinkpad.axtens.net \
--to=dja@axtens.net \
--cc=hanwen@google.com \
--cc=workflows@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox