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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiYh33UCe_sKvLWYY-ptPL6=T4m60b8vCX_t=qvmmOWWg@mail.gmail.com>
Date:   Tue, 24 May 2022 15:00:41 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Ulf Hansson <ulf.hansson@...aro.org>
Cc:     linux-mmc@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] MMC updates for v5.19

On Mon, May 23, 2022 at 5:18 AM Ulf Hansson <ulf.hansson@...aro.org> wrote:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git tags/mmc-v5.19

Please stop doing the horrible undocumented merges.

You have three merge commits that have *no* documentation. They say
"Merge branch 'fixes' into next", and that's it.

If you can't be bothered to explain why and what a merge does, then
just don't do it.

It really is that simple.

I've pulled this, but I really want to stop seeing bad merges.

                    Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ