All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: Date/Time?
Date: Mon, 21 May 2018 16:30:27 -0400	[thread overview]
Message-ID: <8157a65a-51ec-b866-936e-ba59bdd43d5f@redhat.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1805212145070.27054@cbobk.fhfr.pm>

[-- Attachment #1: Type: text/plain, Size: 2038 bytes --]

On 05/21/2018 03:48 PM, speck for Jiri Kosina wrote:
> On Mon, 21 May 2018, speck for Greg KH wrote:
> 
>> Before an hour ago, I didn't know what "keybase" was.  Now that I do 
>> know, I have no idea how in the world anyone submitted kernel patches 
>> using it for ARM people to be basing their code on.
> 
> If Thomas wouldn't set up this list, apparently everything would be 
> happening just on this keybase (whatever that is). I was a bit shocked in 
> the early phases indeed.

> I find it rather ironic that for discussing stuff that allows external 
> websites to steal encryption keys from your browser ... you use ... 
> *drumroll* ... external website :)

Let's skip the FUD tho. It's not a "website". It's an open source
end-to-end encrypted chat application. Its purpose was never to share
patches anyway, just for coordination of issues (you can attach files,
but that was only for convenience). Keybase also wasn't my idea, but I
don't have a problem with it as a useful means of getting many parties
collaborating on coordinated disclosure (think of it as IRC but with an
attempt at actual security that Google, Intel, and others were ok with
using). At the same time, it's great tglx setup this list for Linux
patch discussion. They aren't both trying to solve the same thing.

Specifically on the other arches, at the time they needed to know what
to work on, there was no mailing list anyway (this list wasn't setup for
v4 specific discussion at that time, so those folks could not have been
added to it anyway). They received a copy of the work in progress, by
email as well, and were part of the ongoing discussion so did know each
time Konrad mentioned an updated patch was available. Various of us also
sent copies of the patches. Folks certainly knew who to ping for help.

Regardless of how things should or should not be done, folks were
certainly well aware that things were coming today, months ago.

Jon.

-- 
Computer Architect | Sent from my Fedora powered laptop


  reply	other threads:[~2018-05-21 20:30 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-19 17:26 [MODERATED] Date/Time? Greg KH
2018-05-19 17:51 ` [MODERATED] Date/Time? Borislav Petkov
2018-05-19 18:45   ` Linus Torvalds
2018-05-19 19:07     ` [MODERATED] " Borislav Petkov
2018-05-19 19:48       ` Linus Torvalds
2018-05-19 20:22         ` [MODERATED] " Borislav Petkov
2018-05-20 20:58     ` Jon Masters
2018-05-19 18:21 ` David Woodhouse
2018-05-19 19:05   ` Greg KH
2018-05-20 19:23   ` David Woodhouse
2018-05-20 23:01   ` David Woodhouse
2018-05-21  8:35     ` Greg KH
2018-05-20 17:45 ` Jiri Kosina
2018-05-20 18:19   ` Greg KH
2018-05-20 18:35     ` Borislav Petkov
2018-05-20 19:57       ` Greg KH
2018-05-20 18:36     ` Linus Torvalds
2018-05-20 18:48       ` Jiri Kosina
2018-05-20 20:59 ` Jon Masters
2018-05-20 21:09   ` Jiri Kosina
2018-05-21  6:11     ` Greg KH
2018-05-20 21:48   ` Linus Torvalds
2018-05-20 21:56     ` David Woodhouse
2018-05-21  6:16   ` Greg KH
2018-05-21  7:18     ` David Woodhouse
2018-05-21 15:23       ` Date/Time? Thomas Gleixner
2018-05-21 16:46   ` [MODERATED] Date/Time? Greg KH
2018-05-21 17:12     ` Konrad Rzeszutek Wilk
2018-05-21 19:42       ` Greg KH
2018-05-21 19:48         ` Jiri Kosina
2018-05-21 20:30           ` Jon Masters [this message]
2018-05-22  8:00             ` Peter Zijlstra
2018-05-22  9:26               ` Greg KH
2018-05-22 16:32                 ` Andi Kleen
2018-05-23 14:15                 ` Jon Masters
2018-05-21 17:22     ` Jon Masters
2018-05-21 18:56       ` Date/Time? Thomas Gleixner
2018-05-21 19:16         ` [MODERATED] Date/Time? Jon Masters
2018-05-21 20:43           ` Greg KH
2018-05-21 17:31     ` Jon Masters
2018-05-21 18:53     ` Date/Time? Thomas Gleixner

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=8157a65a-51ec-b866-936e-ba59bdd43d5f@redhat.com \
    --to=jcm@redhat.com \
    --cc=speck@linutronix.de \
    /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.