From: Chris Mason <clm@fb.com>
To: "Theodore Ts'o" <tytso@mit.edu>, Felipe Balbi <balbi@ti.com>,
<rob@landley.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linux-doc@vger.kernel.org>
Subject: Re: [PATCH] Documentation: SubmittingPatches: mention our new Facebook group
Date: Tue, 1 Apr 2014 16:44:37 -0400 [thread overview]
Message-ID: <533B2535.9070107@fb.com> (raw)
In-Reply-To: <20140401203208.GB30033@thunk.org>
On 04/01/2014 04:32 PM, Theodore Ts'o wrote:
> One suggestion: the documentation should add a tip that if you can't
> get someone to review your post, one option is to pay Facebook to
> promote your post[1] so it shows more prominently (or at all) on more
> kernel dvelopers' streams:
A fine idea! I prefer the big newsfeed ads with video. I really want
to see the emotion behind your patch submission.
-chris
next prev parent reply other threads:[~2014-04-01 20:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 14:41 [ANNOUNCE] New Linux Patch Review Group Chris Mason
2014-04-01 15:16 ` 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-01 16:08 ` [PATCH] Documentation: SubmittingPatches: mention our new Facebook group Felipe Balbi
2014-04-01 16:23 ` Steven Rostedt
2014-04-01 20:42 ` Zhan Jianyu
2014-04-01 20:12 ` David Cohen
2014-04-01 20:32 ` Theodore Ts'o
2014-04-01 20:44 ` Chris Mason [this message]
2014-04-01 22:56 ` Steven Rostedt
2014-04-01 23:37 ` Eric Dumazet
2014-04-01 23:38 ` Felipe Balbi
2014-04-01 23:50 ` Joe Perches
2014-04-02 1:39 ` [ANNOUNCE] New Linux Patch Review Group Li Zefan
2014-04-02 13:01 ` Chris Mason
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=533B2535.9070107@fb.com \
--to=clm@fb.com \
--cc=balbi@ti.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=tytso@mit.edu \
/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