linux-kernel - Re: linux-next: Fixes tag needs some work in the drivers-x86 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] [day] [month] [year] [list]

Message-ID: <20201130185851.0884bd9f@canb.auug.org.au>
Date:   Mon, 30 Nov 2020 18:58:51 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Hans de Goede <hdegoede@...hat.com>
Cc:     Mark Gross <mark.gross@...el.com>,
        Vadim Pasternak <vadimp@...dia.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the drivers-x86 tree

Hi Hans,

On Mon, 30 Nov 2020 08:43:21 +0100 Hans de Goede <hdegoede@...hat.com> wrote:
>
> Question, how important is it to fix these ? I normally never do forced pushes
> to the for-next branch. But if this is considered important to fix I guess I
> can make an exception.

I think it is fine to leave these, but to try to not have more in the future.

> Will git rewrite the commit msg when this is set ?  I'm at 2.28 and don't
> have core.abbrev set. But I guess this needs to be set in the gitconfig
> of the creator of the patch; and this has no impact on "git am" ?

It will not rewrite the commit message.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped