Lines Matching refs:author
171 added to the project's release notes at the author's or code reviewer's
260 * If you're not the original author, ensure the 'Author' property of the commit is
261 set to the original author and the 'Committer' property is set to yourself.
263 ``git commit --amend --author="John Doe <[email protected]>"`` to correct the
264 author property if it is incorrect. See `Attribution of Changes`_ for more
319 original commit thread with the reverting patch author.
339 * In general, if the author themselves would revert the change per these
341 author. This is one of the major cases where our norms differ from others;
359 revert. This serves as both a notice to the original author that their
368 provide a means for the patch author to debug the root issue. If a situation
370 requires hardware patch author doesn't have access to, sharp regression in
372 proactive about working with the patch author to debug and test candidate
378 we encourage you to reply to the commit thread, give the author a bit to
379 respond, and then proceed with the revert if the author doesn't seem to be
526 commit access may commit it for the author once appropriate (based on the
540 etc.). The author should first submit them to the relevant project's commit
545 author and the committer like git does. As such, older commits used a different
679 (if available) or email the author, explain the problem and how this impacts