linux-kernel - Re: [GIT PULL] VFIO updates for v6.10-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHk-=wjGbNWK6aOcprocyO8qLySpzJ5-eZzC3if=gb-Fh8NsiA@mail.gmail.com>
Date: Mon, 20 May 2024 16:09:13 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Alex Williamson <alex.williamson@...hat.com>
Cc: "kvm@...r.kernel.org" <kvm@...r.kernel.org>, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] VFIO updates for v6.10-rc1

On Mon, 20 May 2024 at 16:03, Alex Williamson
<alex.williamson@...hat.com> wrote:
>
> Sorry.  In my case I've looked through logs and I've seen bare merges in
> the past and I guess I assumed the reasoning here would be more obvious.

Yeah, the bare merges in the past is why I'm so frustrated about this
all. I don't understand why this keeps happening so much.

Who do people keep doing this thing where they just think "I don't
need to explain this thing".

Yes, git made merges easy. It was one of the design goals, since (a) I
do a lot of them and (b) it's what EVERY OTHER SCM historically
absolutely sucked at.

But just because merging used to be hard, and git made it so easy,
doesn't mean that people should then not even explain them.

I complained to Andrew this merge window about one of his pull
requests that had _seven_ pointless and totally unexplained merges.
It's like people do this operation in their sleep or something, and
don't think about how big an operation a merge is.

            Linus