From: Chris Mason <clm@fb.com>
To: <linux-kernel@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: [ANNOUNCE] New Linux Patch Review Group
Date: Tue, 1 Apr 2014 10:41:04 -0400 [thread overview]
Message-ID: <533AD000.307@fb.com> (raw)
Hello everyone,
During last week's Collab summit, Jon Corbet suggested we use the power
of social media to improve the Linux kernel patch review process.
We thought this was a great idea, and have been experimenting with a new
Facebook group dedicated to patch discussion and review. The new group
provides a dramatically improved development workflow, including:
* One click patch or comment approval
* Comments enhanced with pictures and video
* Who has seen your patches and comments
* Searchable index of past submissions
* A strong community without anonymous flames
To help capture the group discussion in the final patch submission,
we suggest adding a Liked-by: tag to commits that have been through
group review.
To use the new group, please join:
https://www.facebook.com/groups/linuxpatches/
Once you've joined, you can post patches in the group, or email patches to
linuxpatches@groups.facebook.com
-chris
next reply other threads:[~2014-04-01 14:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 14:41 Chris Mason [this message]
2014-04-01 15:16 ` [ANNOUNCE] New Linux Patch Review Group Boaz Harrosh
2014-04-01 15:24 ` Josh Boyer
2014-04-01 15:47 ` Steven Rostedt
2014-04-01 15:40 ` Chris Mason
2014-04-01 15:55 ` Felipe Balbi
2014-04-01 21:33 ` Christian Stroetmann
2014-04-01 22:02 ` Richard Weinberger
2014-04-01 22:20 ` Christian Stroetmann
2014-04-01 22:55 ` Steven Rostedt
2014-04-01 23:11 ` Christian Stroetmann
2014-04-02 1:39 ` Li Zefan
2014-04-02 13:01 ` Chris Mason
2014-04-03 19:57 ` Alex Elsayed
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=533AD000.307@fb.com \
--to=clm@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).