linux-kernel - Re: [PATCH] Documentation: Update CPU hotplug and move it to core-api

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: <20170104090504.wx6ypdk4bx2zfn4n@linutronix.de>
Date:   Wed, 4 Jan 2017 10:05:23 +0100
From:   Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:     Jani Nikula <jani.nikula@...ux.intel.com>
Cc:     linux-kernel@...r.kernel.org, tglx@...utronix.de, rt@...utronix.de,
        Jonathan Corbet <corbet@....net>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Rusty Russell <rusty@...tcorp.com.au>,
        Srivatsa Vaddagiri <vatsa@...ibm.com>,
        Ashok Raj <ashok.raj@...el.com>,
        Joel Schopp <jschopp@...tin.ibm.com>, linux-doc@...r.kernel.org
Subject: Re: [PATCH] Documentation: Update CPU hotplug and move it to core-api

On 2016-12-23 10:03:09 [+0200], Jani Nikula wrote:
> > --- /dev/null
> > +++ b/Documentation/core-api/cpu_hotplug.rst
> > @@ -0,0 +1,372 @@
> > +=========================
> > +CPU hotplug in the Kernel
> > +=========================
> > +
> > +:Date: December, 2016
> > +:Author: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
> > +          Rusty Russell <rusty@...tcorp.com.au>,
> > +          Srivatsa Vaddagiri <vatsa@...ibm.com>,
> > +          Ashok Raj <ashok.raj@...el.com>,
> > +          Joel Schopp <jschopp@...tin.ibm.com>
> 
> Just a drive-by comment, does that do what you want? You might want to
> see if adding one :Author: line per author produces better results.

I see an Author: line for each author, I like better the way it is.

> That said, I think git will do a better job of maintaining both the date
> and the authorship.

If you see the generated html output in your browser you don't have git
around to check the date or the Author. The date should help you to keep
track of the latest version. As for the Author, git would only show me
as the author but I did not write everything myself. Some parts are
still from old documentation.

> BR,
> Jani.

Sebastian