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]
Date:   Tue, 7 Aug 2018 18:57:14 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Nick Desaulniers <ndesaulniers@...gle.com>
cc:     hpa@...or.com, david.laight@...lab.com,
        LKML <linux-kernel@...r.kernel.org>, jdelvare@...e.de,
        Ingo Molnar <mingo@...nel.org>,
        linux-tip-commits@...r.kernel.org, sedat.dilek@...il.com
Subject: Re: [tip:x86/urgent] x86/irqflags: Provide a declaration for
 native_save_fl

On Tue, 7 Aug 2018, Nick Desaulniers wrote:
> On Tue, Aug 7, 2018 at 12:29 AM Thomas Gleixner <tglx@...utronix.de> wrote:
> > On Mon, 6 Aug 2018, Nick Desaulniers wrote:
> > > also, there were tested by's reported:
> > >
> > > Tested-by: David Laight <david.laight@...ab.com>
> > > Tested-by: Sedat Dilek <sedat.dilek@...il.com>
> >
> > Which came in after I applied it....
> 
> I've seen other maintainers revise commit messages before sending pull
> requests along, but I guess that's problematic as anyone else who has
> pulled before the revision would then have a merge conflict.

In general I avoid redoing commits for that reason and others and one of
the reasons why we have the Link: tag in the commit message is to be able
to look up such additional information easily - assumed that the archives
have not vanished from the planet.

Thanks,

	tglx

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ