On 16.09.2018 21:22, Linus Torvalds wrote:
Hi,
> One was simply my own reaction to having screwed up my scheduling of
> the maintainership summit: yes, I was somewhat embarrassed about
> having screwed up my calendar, but honestly, I was mostly hopeful that
> I wouldn't have to go to the kernel
On 04.10.2018 16:57, Eric W. Biederman wrote:
> Very often people will propose patches that do solve their specific case
> but only do 10% or maybe 20% of what is needed for a general kernel
> level solution. For something that just works and does not cause
> maintenance problems in the long run.
On 18.09.2018 03:30, Pavel Snajdr wrote:
Hi folks,
I usually try to stay out of political issues in software projects
(there're already too much real political problems, where people need
to stand up and push away actual oppressors), but now I have the bad
feeling that political (or more precisel
Pavel Snajdr writes:
>
> We started our organization (vpsFree.org) on top of OpenVZ patch set and are
> now
> working to get vanilla up to the task of replacing the venerable 2.6.32-based
> OpenVZ 6 Linux-like thing. The new Code of Conduct is a guarantee for us, that
> we won't be laughed out of
On Sun, Sep 30, 2018 at 3:07 PM, Martin Steigerwald wrote:
> l...@lkcl.net - 30.09.18, 14:09:
>> the third is how UNICEF trains teachers to treat children as human
>> beings.
>
> During releasing a lot of limiting "stuff" I found that probably nothing
> written or said can hurt my feelings unles
l...@lkcl.net - 30.09.18, 14:09:
> > That written: Quite some of the rude mails that contained swearwords
> > I read from you have been about code, not persons. I think this is
> > an important distinction. I do not have much of an issue with
> > swearing at code :), especially when it is in some h
> That written: Quite some of the rude mails that contained swearwords I
> read from you have been about code, not persons. I think this is an
> important distinction. I do not have much of an issue with swearing at
> code :), especially when it is in some humorous way.
absolutely, and this is
https://linux.slashdot.org/story/18/09/27/1529236/linus-torvalds-on-linuxs-code-of-conduct#comments
linus: ah... um... okay so this is beginning to remind me of dr who
films, the comedy film "the world's end", and various other b-movie
horror shows where people were taken over through mind-control
linus, hi,
i haven't been able to get hold of a copy of "invisible dynamics" yet
however my partner did track down a... "translation" of the six
systemic laws from family to organisational principles (from where
they were originally derived). the book puts the systemic laws in a
clearer way and e
Hi Pavel,
and how about if we viewed the new Code of Conduct as about the same
thing as BitKeeper was for the development process?
You should view the Code of Conduct for what it is, as I referenced
previously with real world examples, the evidence shows that it is just
a ploy to take control
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8a104f8b5867c682d994ffa7a74093c54469c11f
ahh, guys? ah... i'm going to try *really* hard to follow the advice
that's listed here ok?
http://www.pndc.com/documents/_PDF%20Text-PNDC%20WORKS.pdf it's a
little challenging
On 2018-09-17 23:09, Michael Woods wrote:
The Code of Conflict was perfectly fine. Whomever convinced you to add
the Code of Conduct was convincing you to give control over to a
social justice initiative that has no interest in the kernel's core
function or reason for existence.
Hi Michael,
Hi Linus,
> The one change that stands out and merits mention is the code of
> conduct addition...
The Code of Conflict was perfectly fine. Whomever convinced you to add
the Code of Conduct was convincing you to give control over to a social
justice initiative that has no interest in the kerne
On Sun, 2018-09-16 at 12:22 -0700, Linus Torvalds wrote:
> Greg Kroah-Hartman (1):
> Code of Conduct: Let's revamp it.
I believe it would be better if this sort of change
had on-list and public discussion before being applied.
On Sun, Sep 16, 2018 at 12:22:43PM -0700, Linus Torvalds wrote:
> [ So this email got a lot longer than I initially thought it would
> get, but let's start out with the "regular Sunday release" part ]
>
> Another week, another rc.
>
Build results:
total: 135 pass: 134 fail: 1
Failed buil
The new kernel rc release is good news as always. The rest of this? not
so much.
"I can’t wait for the mass exodus from Linux now that it’s been
infiltrated by SJWs. Hahahah" -- @CoralineAda on Twitter [1][2]
You really want people like this attempting to sabotage FOSS projects?
I for one am not
hi linus,
just saw the note on slashdot. i just wanted to say how amazed,
relieved and delighted i was to see what you wrote. that you
recognised that you needed to reflect, *sought feedback*, and, most
importantly, were willing and able to discuss that and ask publicly.
as the longest-serving c
Hi Linus.
I was "around linux-kernel" some 10 years ago and still to this date
sometimes check e.g. lkml.org where I happened upon this; felt it hard
to resist commenting on one specific bit...
Whereas you concentrate on net-positive effect on code quality of an at
times "crass" communication sty
[ So this email got a lot longer than I initially thought it would
get, but let's start out with the "regular Sunday release" part ]
Another week, another rc.
Nothing particularly odd stands out on the technical side in the
kernel updates for last week - rc4 looks fairly average in size for
this
20 matches
Mail list logo
