Linux Kernel Summit discussions
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Joe Perches <joe@perches.com>, Theodore Ts'o <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Talking code or talking in code!
Date: Fri, 31 May 2019 10:34:05 -0600	[thread overview]
Message-ID: <646f1289-52fa-de85-9ce8-cfaa47080c2f@linuxfoundation.org> (raw)
In-Reply-To: <465097adab87fe60008a826e51ee09a80a03d157.camel@perches.com>

On 5/31/19 10:25 AM, Joe Perches wrote:
> On Fri, 2019-05-31 at 09:42 -0600, Shuah Khan wrote:
>> Isabella sent in a proposal for a BOF session at LPC. She is looking
>> to social her research
> 
> What does it mean to social her research?

It is supposed to be socialize - In any case, what I meant to say is
that she is looking for feedback and real data to fine tune her
research and tool.

> 
>> and more importantly, she is looking to validate
>> her analysis engine with real data.
> 
> I expect validation will always be a difficult proposition.
> case in point is the phrase "social her research".
> 
> 

Please see above. It is a typo on my part.

thanks,
-- Shuah

  reply	other threads:[~2019-05-31 16:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 22:19 [Ksummit-discuss] [MAINTAINERS SUMMIT] Talking code or talking in code! Shuah Khan
2019-05-31  2:14 ` Theodore Ts'o
2019-05-31  2:42   ` Matthew Wilcox
2019-05-31 12:12     ` Laura Abbott
2019-05-31 15:54       ` Shuah Khan
2019-05-31 15:42   ` Shuah Khan
2019-05-31 16:25     ` Joe Perches
2019-05-31 16:34       ` Shuah Khan [this message]
2019-06-03 15:51     ` Mark Brown
2019-06-03 17:39       ` Shuah Khan
2019-07-28 22:05         ` [Ksummit-discuss] [MAINTAINERS SUMMIT] (withdrawn) " Shuah Khan

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=646f1289-52fa-de85-9ce8-cfaa47080c2f@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).