From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [patchwork-bot@kernel.org] Patchwork summary for: Linux amlogic development
Date: Wed, 28 Nov 2018 22:28:37 -0800 [thread overview]
Message-ID: <7hlg5cwg6i.fsf@baylibre.com> (raw)
FYI...
I'm experimenting with a new patchwork-bot kernel.org service[1] which
will automatically update the patchwork I use for tracking linux-amlogic
patches[2] when I push patches to my tree. it is also sending me summary
reports (like the one below) when it updates the patchwork status.
Also, it can optionally notify the submitter directly when their patches
are applied (see [1] for more details on the notification submitters
would receive.)
Since I'm an early adopter of this service, I've chosen for now to not
enable the "notify subscriber" option, but for those of you who are
submitting patches, would you want to get these automatic notifications
when your patches are merged into my tree? Note that these
notifications are for when they merge into *my* tree, which means they
are queued for the next merge window, but not yet in arm-soc or
mainline.
Kevin
[1] https://korg.wiki.kernel.org/userdoc/patchwork
[2] https://patchwork.kernel.org/project/linux-amlogic/list/
-------------- next part --------------
An embedded message was scrubbed...
From: patchwork-bot@kernel.org
Subject: Patchwork summary for: Linux amlogic development
Date: Thu, 29 Nov 2018 01:20:22 +0000
Size: 10702
URL: <http://lists.infradead.org/pipermail/linux-amlogic/attachments/20181128/f5b679d3/attachment.mht>
reply other threads:[~2018-11-29 6:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7hlg5cwg6i.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@lists.infradead.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