From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
rt@linutronix.de, Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Srivatsa Vaddagiri <vatsa@in.ibm.com>,
Ashok Raj <ashok.raj@intel.com>,
Joel Schopp <jschopp@austin.ibm.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: Update CPU hotplug and move it to core-api
Date: Wed, 4 Jan 2017 10:05:23 +0100 [thread overview]
Message-ID: <20170104090504.wx6ypdk4bx2zfn4n@linutronix.de> (raw)
In-Reply-To: <878tr7rs1u.fsf@intel.com>
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@linutronix.de>,
> > + Rusty Russell <rusty@rustcorp.com.au>,
> > + Srivatsa Vaddagiri <vatsa@in.ibm.com>,
> > + Ashok Raj <ashok.raj@intel.com>,
> > + Joel Schopp <jschopp@austin.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
next prev parent reply other threads:[~2017-01-04 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 16:19 [PATCH] Documentation: Update CPU hotplug and move it to core-api Sebastian Andrzej Siewior
2016-12-23 8:03 ` Jani Nikula
2017-01-04 9:05 ` Sebastian Andrzej Siewior [this message]
2017-01-04 11:19 ` Jani Nikula
2017-01-13 17:34 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170104090504.wx6ypdk4bx2zfn4n@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=ashok.raj@intel.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rt@linutronix.de \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=vatsa@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).