From: Lee Jones <lee.jones@linaro.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>,
users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: New version of lore available for preview
Date: Thu, 9 Sep 2021 15:04:48 +0100 [thread overview]
Message-ID: <YToUgHL2V/lci+Df@google.com> (raw)
In-Reply-To: <20210909095514.49e68456@gandalf.local.home>
On Thu, 09 Sep 2021, Steven Rostedt wrote:
> On Thu, 9 Sep 2021 14:32:25 +0100
> Lee Jones <lee.jones@linaro.org> wrote:
>
> > Well, as beautifully inefficient as that all sounds, it might be
> > slightly less time consuming if I just succumb to peer pressure and
> > switch pwclient out for b4.
>
> The old "Show them an even more painful alternative to make the current
> solution seem good" trick.
Works every time! :)
> > Thankfully, my use-case is much simpler than Steven's.
>
> Of course, my solution came before b4 was even thought of (I even mentioned
> this solution in the kernel summit discussion that started the path to b4).
>
> The one thing I need that b4 doesn't give me, is a place outside of email
> to keep track of the state of patches. I've failed in all my attempts at
> using email folders to do this. What I love about patchwork is that I can
> keep the patches at various states.
>
> New - I just received it and need to look at it / test it.
>
> Under review - They have been tested, just need to be pushed to upstream.
>
> Accepted - they have been accepted.
>
> I also created other states for topics, like "Real Time", "Scheduler",
> "RCU", etc, so that I can go back if I have time (which currently I never
> do), and look at these patches.
>
> I also use the "delegate" option to assign patches to myself that are high
> in priority.
>
> I tried doing this with email folders, and even a git repo, but because I
> use email and git for so much else, it still gets lost in the noise. I like
> patchwork because its web based, and I have a window up all the time that
> shows me what patches I need to work on next.
>
> The pulling into git is actually one of the trivial parts of the process.
I like to keep my setup as KISS as possible.
Fortunately, in terms of upstream reviews I've managed to whittle
patches down into 3 states;
- unread
- does not need review
- needs review
The latter is represented with Mutt's 'flag-message' functionality.
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2021-09-09 14:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 19:07 New version of lore available for preview Konstantin Ryabitsev
2021-08-18 19:09 ` Jason A. Donenfeld
2021-08-18 19:48 ` Konstantin Ryabitsev
2021-08-18 19:50 ` Junio C Hamano
2021-08-25 16:30 ` Rob Herring
2021-08-25 16:44 ` Konstantin Ryabitsev
2021-08-25 21:39 ` Josh Triplett
2021-08-26 14:04 ` Konstantin Ryabitsev
2021-08-26 23:04 ` Josh Triplett
2021-09-02 19:53 ` Jason Gunthorpe
2021-09-02 20:14 ` Konstantin Ryabitsev
2021-09-02 22:44 ` Masahiro Yamada
2021-09-03 10:30 ` Mark Brown
2021-09-03 15:21 ` Konstantin Ryabitsev
2021-09-06 9:59 ` Lee Jones
2021-09-08 18:37 ` Konstantin Ryabitsev
2021-09-09 12:49 ` Steven Rostedt
2021-09-09 13:32 ` Lee Jones
2021-09-09 13:38 ` Konstantin Ryabitsev
2021-09-09 13:45 ` Lee Jones
2021-09-09 14:39 ` Konstantin Ryabitsev
2021-09-09 15:24 ` James Bottomley
2021-09-09 16:17 ` Konstantin Ryabitsev
2021-09-09 14:51 ` Alexandre Belloni
2021-09-09 15:00 ` Konstantin Ryabitsev
2021-09-09 13:43 ` Greg KH
2021-09-09 13:54 ` Lee Jones
2021-09-09 13:56 ` Mark Brown
2021-09-09 14:05 ` Lee Jones
2021-09-10 16:07 ` Bjorn Andersson
2021-09-10 16:12 ` Mark Brown
2021-09-10 17:21 ` Peter Zijlstra
2021-09-09 13:55 ` Steven Rostedt
2021-09-09 14:04 ` Lee Jones [this message]
2021-09-09 14:51 ` Peter Zijlstra
2021-09-10 6:10 ` Lee Jones
2021-09-02 23:38 ` Jason Gunthorpe
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=YToUgHL2V/lci+Df@google.com \
--to=lee.jones@linaro.org \
--cc=jgg@nvidia.com \
--cc=konstantin@linuxfoundation.org \
--cc=masahiroy@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.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 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.