linux-kernel - Re: linux-next: Fixes tag needs some work in the hyperv-fixes 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]

Date:   Mon, 15 Jul 2019 08:01:59 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Sasha Levin <sashal@...nel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the hyperv-fixes tree

Hi Randy,

On Sun, 14 Jul 2019 08:02:11 -0700 Randy Dunlap <rdunlap@...radead.org> wrote:
>
> > Please do not split Fixes tags over more than one line.  Also do not
> > include blank lines among the tag lines.  
> 
> Hm, so you are saying that the Fixes: line should not be separated from the
> other tag lines?  That's news to me...

see "git interpret-trailers".

> Should Fixes: be before the other tag lines or does it matter?

I don't think that matters, but first seems most used.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped