linux-kernel - Re: Improvement suggestion for creation of next [Was: linux-next: manual merge of the dmaengine tree with the driver-core tree]

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: <20210916095229.cvsjr4wbro26gev7@pengutronix.de>
Date:   Thu, 16 Sep 2021 11:52:29 +0200
From:   Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: Improvement suggestion for creation of next [Was: linux-next:
 manual merge of the dmaengine tree with the driver-core tree]

Hello Stephen,

On Thu, Sep 16, 2021 at 04:27:40PM +1000, Stephen Rothwell wrote:
> [Sorry this took so long]

No problem. Thanks for picking up my suggestion (and not loosing it in
your mailbox).

> I prefer to fetch all the trees (and run my checking scripts across
> them independently of the merge/build cycle.  However, I have improved
> the merge commit messages (I think).  Please check out today's
> linux-next.

Looks great. Thanks.

> I have decided to remove the SHA1 from the message, as you
> can see that from what is merged anyway.

I understand that starting from tomorrow the short log will be shorter
for the merge commits.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)