From: Jani Nikula <jani.nikula@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [maintainer-tools PATCH] drm-intel: Fix links to torvalds documentation.
Date: Mon, 10 Jul 2017 13:27:58 +0300 [thread overview]
Message-ID: <87van0powh.fsf@nikula.org> (raw)
In-Reply-To: <1499371342-9195-1-git-send-email-rodrigo.vivi@intel.com>
On Thu, 06 Jul 2017, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> All process related docs has moved to the new "process" folder,
> but also all .txt migrated to .rst as well.
We could point at the generated documentation at [1] or [2] instead of
git trees now.
BR,
Jani.
[1] https://www.kernel.org/doc/html/latest/
[2] https://01.org/linuxgraphics/gfx-docs/drm/
>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drm-intel.rst | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/drm-intel.rst b/drm-intel.rst
> index 4699171..5dcb7d8 100644
> --- a/drm-intel.rst
> +++ b/drm-intel.rst
> @@ -188,8 +188,8 @@ The maintainers will cherry-pick labeled patches from drm-intel-next-queued to
> the appropriate branches.
>
> If possible, the commit message should also contain a Fixes: tag as described in
> -`Documentation/SubmittingPatches
> -<https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches>`_
> +`Documentation/process/submitting-patches
> +<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst>`_
> to aid the maintainers in identifying the right branch.
>
> Requesting Fixes Cherry-Pick Afterwards
> @@ -199,7 +199,7 @@ It's not uncommon for a patch to have been committed before it's identified as a
> fix needing to be backported.
>
> If the patch is already in Linus' tree, please follow `stable kernel rules
> -<https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/stable_kernel_rules.txt>`_.
> +<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst>`_.
>
> Otherwise, send an email to intel-gfx@lists.freedesktop.org and
> drm-intel-fixes@lists.freedesktop.org containing the subject of the patch, the
> @@ -359,8 +359,9 @@ Detail Check List
>
> An inexhaustive list of details to check:
>
> -* The patch conforms to `Documentation/SubmittingPatches
> - <https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches>`_.
> +* The patch conforms to `Documentation/process/submitting-patches
> +
> + <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst>`_
>
> * The commit message is sensible, and includes adequate details and references.
>
> @@ -409,8 +410,8 @@ On Confidence, Complexity, and Transparency
> list, IRC, in person, in a meeting) but must be added to the commit.
>
> * Reviewed-by. All patches must be reviewed, no exceptions. Please see
> - "Reviewer's statement of oversight" in `Documentation/SubmittingPatches
> - <https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches>`_
> + "Reviewer's statement of oversight" in `Documentation/process/submitting-patches
> + <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst>`_
> and `review training
> <http://blog.ffwll.ch/2014/08/review-training-slides.html>`_.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-07-10 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 20:02 [maintainer-tools PATCH] drm-intel: Fix links to torvalds documentation Rodrigo Vivi
2017-07-10 10:27 ` Jani Nikula [this message]
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=87van0powh.fsf@nikula.org \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.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).