linux-kernel - Re: [GIT PULL] MMC updates for v5.19

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: <CAPDyKFreHmOuJ8MLmumTjs-52JxBydtQ3q3SMPCUtMKx89x8wQ@mail.gmail.com>
Date:   Wed, 25 May 2022 09:18:59 +0200
From:   Ulf Hansson <ulf.hansson@...aro.org>
To:     Linus Torvalds <torvalds@...ux-foundation.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 Wed, 25 May 2022 at 00:00, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> 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.

My bad, I have simply forgotten about them lately. Earlier I was more
often doing a re-base of my next branch against some later rc, which
makes the merges to disappear from the history.

>
> 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.

Thanks, I will make sure this doesn't happen again, sorry for the inconvenience.

>
>                     Linus

Kind regards
Uffe